I just ran across this page and thought I should mention how I do vim extensions in perl.

First, I put all the code in a module, which I load from the vim script. All of the mappings and functions I want to define are in the vim script, but they are just stubs for a perl functions, eg

function! s:rowwise_dd() range
    perl VIM::CSV::rowwise_dd
endfunction
nnoremap <buffer> <LocalLeader><Left>   :perl VIM::CSV::prev_col<CR>
[download]

By putting only trivial perl in the vim script, I minimize difficult-to-debug problems that come from mixing perl and vim. Also, things like syntax highlighting work perfectly on the module.

Second, I want the module to syntax-check outside of vim (the major pay-off of step one). This is a simple matter of duplicating the prototypes that vim implicitly sets up, eg

sub VIM::DoCommand ($);
sub VIM::Eval ($);
sub VIM::Msg ($;$);
[download]

I have not made any effort to make my module run outside of vim, as it is quite intimately tied to vim.

Third (my favorite part), some syntactic sugar to make vim commands look like vim commands (this should be its own module, but I'm lazy):

use Filter::Util::Call;
BEGIN {
    filter_add( sub {
        my $status = filter_read;
        return $status unless /^\s*:/;  
        s/"/\\"/g;
        s/:(.*)/VIM::DoCommand "$1";/;  
        return $status;
    })
}
...
    :w
[download]

By the way, the problem that you don't get any output from syntax errors is really a perl bug.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.