$ tail -1 ~/.vilerc
source /home/abigail/.vile.mappings
$ cat ~/.vile.mappings
 1 store-macro
   goto-beginning-of-file
   append-string "#!/usr/bin/perl\n\n"
   append-string "use strict;\n";
   append-string "use warnings;\n";
   set-mode "perlmode"
   position-window b
   open-line-below-and-append-chars
~endm


 2 store-macro
   save-file
   shell-command &cat "perl " $cfilname
~endm


 3 store-macro
   save-file
   shell-command &cat "perl -c " $cfilname
~endm

 4 store-macro
   save-file
   shell-command "make"
~endm


bind-key execute-macro-1 ^A-p
bind-key execute-macro-2 ^A-r
bind-key execute-macro-3 ^A-c
bind-key execute-macro-4 ^A-m
[download]

map ß O#!/usr/bin/perl -w<CR>use strict;<CR>
map Ü :!perl -c %
map ü :!perl %
map ä :!perldoc -f
" debugging
imap debug warn "\n";<ESC>hhhi<C-R>=expand("%:t:r")<CR>
" find perl variables and copy them
map <F10> ?\(\$\\|@\\|%\)<CR>v/\><CR>hy<ESC>h
" debugging
imap ddumper <ESC>gglouse Data::Dumper; $Data::Dumper::Indent = 1; $Da
+ta::Dumper::Sortkeys = 1;<ESC>``
[download]

set makeprg=perl -Mstrict -wc %
set errorformat=%m at %f line %l.
[download]

Now you can just type :make to check the script; Vim's quickfix (:help quickfix) will then pick up perl's error messages. Besides the handy (and very key-bindable :) ) commands to navigate error locations, you can also do a :copen to open a window on a special buffer that lets you visually navigate errors and move to their locations.

If you edit stuff other than Perl code with Vim, you should probably place these somewhere that only sets them for Perl code files. :help ftplugin-override