Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don't think Ovid's code works any more because it relies on an obsolete output format. I fixed up all output to work with the new format in order to support other editors.

    Nowadays all output intended for editors is in the form of a deep data structure. Elisp for Emacs by default, and Vim hashes/collections (or whatever it's called) if you specify --io_type=editor_vim as an option to "perly_sense".

    I neither use nor program Vim though, but anyone who wants to start writing a Vim integration layer would actually be able to get support for the simple things in PerlySense. Start by reading the source for bin/perly_sense and playing with it to see what comes out. (don't trust the sparse docs in that file)

    Things that could work in Vim are basic things like navigating to modules, methods, navigating to base classes, getting docs, running programs (tests mostly) from the correct directory and with the correct @INC set, display the inheritance tree (well, graph), etc. Basic but very useful features.

    Re: your comment about Projects. There is a Project concept [cpan.org], which is used for config and to e.g. determine where the to run things from. Still not for ack'ing and things like that though.

    In spite of the name, PerlySense doesn't do intellisense yet. I'm still picking lower hanging fruit [cpan.org]. And cooler fruit [cpan.org] :)
    • Thanks for your feedback. Now I know why it looks so strange :-)

      I do hope someone will pick up the PerlySense vim ball but I don't program vim and I'm not likely to pick it up anytime soon. The syntax really looks awful :-(

      Perhaps the temptation will be too big one day, but I hope someone familiar with vim programming will come around sooner :-)