Haven't used mode-compile myself before (but will take a look!) I tend to just use M-x compile in my Emacs (normally an emacs -nw on an ssh session to a server) combined with an M-x shell buffer where I run little test iterations from the shell. Something like this in .emacs: (add-hook 'perl-mode-hook
(lambda ()
(unless (or (file-exists-p "makefile")
(file-exists-p "Makefile"))
(set (make-local-variable 'compile-command)
(concat "perl -c "
(file-name-completion buffer-file-name)))
+)))
can bind the default M-x compile to run the perl interpreter on your code and if there are errors hitting Enter on the error message will take you to the offending line in your code buffer.
Having the shell running in an emacs buffer is handy because the whole buffer (or a region of it) can be saved for documentary purposes and you can go back to pick up a command from previously, edit it and re-run it. Since many of my such trials are faking a CGI run (e.g. perl ./blah.pl param1=fred param2=yaada param3=DoIt), it's fairlly easy to tailor and then modify the command from one trial to another.
-
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.
|