(defun perl-dbg ()
"Insert a debugging print statement"
(interactive)
(insert "use Data::Dumper qw( Dumper );\nwarn Dumper [ ];\n")
(search-backward "[ "))
(global-set-key "\C-c\C-p" 'perl-dbg)
Then typing CTL-C CTL-p inserts this text:
use Data::Dumper qw( Dumper );
warn Dumper [ ];
and leaves the cursor under the [ character.
I wasn't sure if you wanted to prompt for the name of the variable(s) to dump, so I changed (defun perl-dbg (name) to (defun perl-dbg (). The statement (interactive) makes it interactive, so that it can be bound to a key combination.
Here's a version that prompts for a variable name (or names):
(defun perl-dbg (name)
"Insert a debugging print statement"
(interactive "svariable to dump: ")
(insert "use Data::Dumper qw( Dumper );\nwarn Dumper ")
(insert name)
(insert ";\n"))
There are probably better ways to handle strings in Emacs-Lisp, but I've only recently started playing with it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|