in reply to How do you run your scripts with vim (or emacs)?

Dunno about vim, but in emacs it's fairly simple: I've got mode-compile on and then it's just a question of typing C-c c ENTER to run the current perl script, with output to a split buffer and clickable error messages (or press C-x ` to go to the next error).

"What should it profit a man, if he should win a flame war, yet lose his cool?"
  • Comment on Re: How do you run your scripts with vim (or emacs)?

Replies are listed 'Best First'.
Re^2: How do you run your scripts with vim (or emacs)?
by jvector (Friar) on Sep 14, 2008 at 21:41 UTC
    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)))
+)))

    [download]
    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.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom