Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of ambs (3914)

Monday July 12, 2004
04:01 PM

Emacs, vi and Perl

[ #19809 ]
I am an emacs user and a vi survivor (I know emacs would be a nice operative system if it had a nice editor). I know that there is a "easy" way to integrate vi and Perl. Meanwhile, emacs is being not so easy. The Perlmacs is from 2000 and Emacs::EPL from 2001.

This means perl hackers do not use emacs, or that emacs is good enough not needing perl integration?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • But I don't have any need for my Emacs to speak Perl, or my Perl to speak Emacs. So no, I've not been all that interested in how it no longer plays tightly together.
    • Randal L. Schwartz
    • Stonehenge
  • Emacs::EPL actually works just fine. I've even tried to develop an interactive Perl mode for Emacs (see "Sepia" on CPAN) -- there may be some infelicities, but I'd be happy to try to fix them. However, I found that I don't tend to develop Perl interactively, though I do so with both Lisp and Octave.
  • I have managed fine for about 7 years just using emacs and the command line.

    The only integration I have ever used in emacs is the Version control so that I have lots of revisions of all the code I am working on, its also handy when using CVS.

    I usually run perldoc, perl -e '$short_perl_code' and CPAN from the command line. perl -cw is something I also prefer to do from the command line, usually outputting stderr to a log.


    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
  • XEmacs plays nicer with Perl. Plus (being on Windows) it is a better "Windows" application.