I completely agree with you about the iterative nature of developing in emacs. It seems that people who haven’t done that kind of thing before don’t understand why it so great!

I hadn’t come across these emacsy perl modules before. So many things to try, so little time

Cheers

Really one of the best parts about writing elisp is the whole iterative bottom-up development process that comes with programming in lisps. I can read elisp docs, experiment in scratch, run, and edit my elisp code in one program! Compiling? Restarting? No thanks.

I had briefly tried to emulate this process with perl by using the Sepia perl module. I did not get very far into using it and gradually forgot about it. Sometimes it takes me a few tries to learn new emacs usage.

Have you tried Sepia, Devel::PerlySense, or Emacs::PDE to try to share emacsen QWAN with perl?

What makes you think I’m trying to drag folks into an editor war? I used to use vim as my primary editor myself and still do for quick edits. But now I’ve found something that works better for me, I would hate to go back.

I think people have pointed out the problems with extrapolating from your poll data previously. I believe the figures on vim vs emacs usage – it tallies with my own experience, but with you writing a perl blog and knowing mostly perl folks, your sample will be hugely biased when you’re talking about language usage.

Besides that, a lot less Perl developers are using Ruby or Python than Perl….
http://perlide.org/poll200911/