Very well organized article!

You could also integrate it with some information on how to execute Perl code from within Vim and how to set embedded syntax for HTML or SQL.
See Editing features for advanced users for a basic introduction.

Other Vim / Perl related nodes:

• Using VIM 6 with Perl
• Perl Editor Voodoo
• VIM 6.0 filetype plugin for Perl
• .vimrc options to assist with perl coding
• vim perl debugger integration
• Perl syntax coloring using vim
• Using vim for highlighting in Perl

update
Also Environments extended with embeded Perl: are they for real? explores Vim and Perl joint usage.

 _  _ _  _  
(_|| | |(_|><
 _|   

Absolutely wonderful! I never knew about vsplit. Now I can have my code and tests side by side in one window! Thank you.

Cheers,
Ovid

New address of my CGI Course.
Silence is Evil (feel free to copy and distribute widely - note copyright text)

I implemented gVim support some time ago but thought I would support PFE completely before releasing it (the DDE support in Editor::Win32::PFE is somewhat shaky, so I'm not sure it'll work at all times). Then I got interested in other things :)

The gVim stuff is done though, but since I don't use the editor myself I'm kind of curious how good it fits the way people actually use gVim. So, if you're interested in beta-testing the gVim stuff, I would be very happy to get your feedback.

1. Download the beta, unzip
2. Start gVim
3. Start Perl Oasis
4. In File | Preferences | Editor, chose gVim
5. Check out Top Headings while you're in the preferences and go back there after trying it out
6. Voila!

TVSET, you ROCK!

Thanks for highlighting taglist and BlockComment; i would not have (bothered to) found (find) them otherwise.

++TVSET. Excellent article. I especially like bg=light and bg=dark. I have long wondered why vim uses different colors with different TERM settings... now I know why, and furthermore how to change the default behavior. Many thanks.

I liked your article very much. But here at the university we have only version 5.6. So I have to try which of your tips work here.

I also found a misprint:

Vim support both vertical and horizontal window splitting. To split current window horizontally execute ":split" while in the normal mode. To split current window horizontally, use ":vsplit" instead.

++TVSET.

Regarding some of the screenshots -- you may want to consider using ":runtime! syntax/2html.vim". Granted, it would not show the results of ":split" or ":vsplit", and produces some rather... ugly html, but would address some of the issues that other monks have raised.

C²

The only thing there I didn't see is the ability to switch to files and modules easily:

set path+=/path/to/modules/**
set suffixesadd=.pm,.pl
set includeexpr=substitute(v:fname,'TMPLDIR','/path/to/tmpl/dir','')
[download]

use Peeron::DB;
[download]

my $tmpl = HTML::Template->New(Filename => "$Peeron::Conf::TMPLDIR/exa
+mple.tmpl");
[download]

-- zigdon

When I used the suggestions, I found 2 things annoying me. I'm not sure whether other Perl programmers would also, but I suppose.

I program with line numbering switched on, but the file/buffer browser has than also the line numbering. That's quite ugly, as I don't need it at these views and it is a simple waste of space. I fixed it with setting an autocmd that do set number only with specific files (like *.p?).

The Perl syntax compiler is of course very useful, but it seems to be written in 2001 where perhaps an older Perl version was outsight. However, the compile command always starts with perl -Wc, so that in all part of the codes warnings are shown. Even in the { no warnings; ... } subparts. That's odd, as I suppose, nowadays with Perl 5.8, using use strict; use warnings; is the standard.
I fixed it with a simple change in perl.vim, replacing setlocal makeprg=perl\ -Wc\ % with setlocal makeprg=perl\ -c\ %.

autocmd BufNewFile,BufRead *.p? map <F1> :Perldoc <cword><CR>
                                                  +++++++
[download]

Very nice article!

But I found two little errors or lazinesses:

• In the section "text-folding" you wrote
  

  " Folding configuration
  set foldmethod=marker
  " Edit and uncomment next line if you want non-default marker
  "set foldmarker="[[[,]]]"
  [download]

  
  I guess you deleted the wrong line and meant
  set foldmarker="{{{,}}}"
  instead of the last line?!

• You used the comment
  " This is for winmanager
  more then once, even in the section "Tag explorer".