perlnow.el 0.41 is out

4 views

Skip to first unread message

Joe Brenner

unread,

Oct 6, 2009, 3:18:41 PM10/6/09

to emacs-perl-...@googlegroups.com

I just pushed perlnow.el version 0.41 out... it's not perfect, but
much better than the recent 0.40, and I really need to take a break
from hacking on this and get back to Real Work.

I did a lightning talk on the new release:

http://www.obsidianrook.com/perlnow/new_release_perlnow_version-0.4.html

The code, documentation, and so on can be found here:

http://www.obsidianrook.com/perlnow/index_docs.html

Here's a try at an elevator pitch:

perlnow.el integrates what might look like two seperate sets of features
at first glance: (1) commands to create new code using templates
(2) a more complex version of mode-compile specifically for perl tasks.

For example, if you're editing a module, and you use a perlnow
command to open a test file, it remembers the association between
the files, and if you then issue the perlnow "run" command from
either of those buffers it will guess that you want to run that
test file. Perlnow also has a version of a "back" command that
makes it easier to rapidly switch between the two buffers
(because these associations are a bit less ephemeral than the
buffer order used by "switch-to-buffer").

And if you use perlnow's "debug" command from either buffer, it
figures you want to run perldb on the test file, even if the
associated module is currently active.

An even shorter pitch:

Just look at the "perlnow-check" command. If you don't have
something like that yet, you need something like it... and my
new version has a cute feature, if I do say so myself: with the
"C-u" prefix it does a "check harder" that runs podchecker and
perlcritic in addition to doing a "perl -cw"

I was asked about backwards compatibility: I don't think this this
release will mess with the expectations of someone who was used to
the 0.3 version, at least not all that much. Most of the new
features are accessed by either entering a new command, or preceeding
an old command with a "C-u" prefix.

(I wish I could say things like this with more certainty, but I'm
still working without a test suite on this project. Really annoying.)