Here are some things to put in your .vimrc file to improve your perl editting experience:
" With these, you can type "K" when you are over a perl term
" in your code, and it will look it up with "perldoc -f $term"
" what I would like to happen is this: perldoc -f term || perldoc term
" So, it tries to look up the keyword as a perl function
" and then it tries to look it up as a module name if that fails
au BufRead,BufNewFile *.pm setlocal keywordprg=perldoc\ -f
au BufRead,BufNewFile *.pl setlocal keywordprg=perldoc\ -f
au BufRead,BufNewFile *.cgi setlocal keywordprg=perldoc\ -f
" You'll have to check for the location of efm_perl.pl on your system
" With this, you can use ":mak", and will run your script through
" 'perl -cw' and allow you to easily edit the results
set makeprg=/usr/local/share/vim/vim61/tools/efm_perl.pl\ -c\ %\ $*
set errorformat=%f:%l:%m
You may also be interested in My Life with Text Editors
-mark
-
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.
|
