![\"\"](\"\/wordpress\/wp-content\/20040421-vim.png\")
This is my attempt to provide a clear and simple instructions on adopting Vim text editor for programming needs. I am using Perl as the programming language in the examples, but most of this document will apply equally for any other programming language.<\/p>\n
Update:<\/ins> This post was translated into Portuguese<\/a> by Alceu Rodrigues de Freitas Junior.<\/p>\n <\/p>\n <\/p>\n <\/a><\/p>\n <\/p>\n <\/a><\/p>\n This document is my attempt to provide a clear and simple instructions on adopting Vim text editor for programming needs. I am using Perl programming language as specific example, although most of this document will apply equally for any other programming language.<\/p>\n Some people may argue that Vim does not need any additional configuration to cover programming needs, while others will say it will never be as good as some Integrated Development Environments (IDEs). I am not going to argue about these two points of view, but rather provide several tips on how to bring a simple text editor, as seen by some, closer to look and feel of an IDE, as needed by others.<\/p>\n <\/p>\n <\/a><\/p>\n First of all, this document is for people who are already using Vim for their programming tasks. Those people who feel that there is something missing in Vim should definitely read this document. People who recently stopped using Vim due to the reason that something was not there should also read this document.<\/p>\n <\/p>\n <\/a><\/p>\n I assume that the reader has Vim installed on the system and is comfortable with simple text editing in Vim.<\/p>\n Another assumption is that the reader has at least basic experience in configuring Vim by means of the I assume that the reader is using a UNIX\/Linux machine for Vim editing sessions. Otherwise, shell command line examples should be taken as a pseudo code for algorithm. :)<\/p>\n The last but the least assumption is that the reader has access to the Internet and knows how to browse web sites and download files.<\/p>\n <\/p>\n <\/a><\/p>\n Document is separated into two parts: “Basic Configuration<\/a>” and “Advanced Configuration<\/a>“. “Advanced Configuration<\/a>” is further split into “Common Configuration<\/a>” and “Perl-Specific Configuration<\/a>“.<\/p>\n “Basic Configuration<\/a>” contains examples of simplest Vim configuration that does not even require Internet connectivity. These are usually plain Vim configuration options which are built-in.<\/p>\n “Advanced Configuration<\/a>” contains examples Vim plug-in installation and configuration. You will need Internet connectivity to follow this section.<\/p>\n If you use Vim for your programming tasks, but do not use Perl programming language, then “Common Configuration<\/a>” section is for you. Examples in “Perl-Specific Configuration<\/a>” section can be used for extending Vim support for other programming languages.<\/p>\n <\/p>\n <\/a><\/p>\n In order to provide a guaranteed working examples, I have created a new user “codemonkey” on my fully updated RedHat Linux 7.3 home server. This user has no prior I have created an empty Each feature installation and\/or configuration is explained separately and can be done independently of the others. Screenshots are provided, where appropriate.<\/p>\n <\/p>\n <\/a><\/p>\n Vim has a large community with a lot of friendly and supportive members. If you are using Vim or just planning to do so, I suggest that you subscribe to Vim mailing list at http:\/\/www.vim.org\/community.php<\/a>.<\/p>\n Visit the Vim website for a collection of Tips and Plug-ins at http:\/\/www.vim.org\/<\/a>.<\/p>\n Vim is shipped with an extensive documentation which you can find in <\/p>\n <\/a><\/p>\n <\/p>\n <\/a><\/p>\n <\/p>\n <\/a><\/p>\n Tabulation is one of the hottest topics in programmers discussions when it comes to style. A very nice explanation of what is the problem with tabulations and spaces can be read at http:\/\/www.jwz.org\/doc\/tabs-vs-spaces.html<\/a>. I must say though, that I don’t agree with author’s position on the subject.<\/p>\n The article does provide you with several options for vi\/Vim configuration to control the behavior of the tabs. I will just add\/repeat the ones I consider important.<\/p>\n Add “ Add “ Vim allows you to select a block of code and change it’s indentation level (either increase or decrease the level). Control the width of the indentation level with “ While you are in the command mode, Vim can complete the names of files and directories in case you want to open or save a file. In order to complete a file or a directory name you should start typing it’s name on the command prompt and then press the completion key. You can change the completion key to be almost anything you want with “ If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n If you still don’t like the appearance of the code, stay tuned until “Color schemes<\/a>” discussion.<\/p>\n If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n One of Vim’s features I cannot live without is text completion. When editing, press If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n Vim supports both vertical and horizontal window splitting. To split current window horizontally execute “ If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n Vim will show both files in vertical split window mode. When you will scroll in one window, Vim will automatically scroll another window for you. You can patch the individual differences using If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n Vim supports six folding methods: by indent, by expression, by syntax, by changes in the text, by marker, and manual folding. It is up to you which method to use. For the sake of the example, I will show how to configure folding by marker.<\/p>\n In order to tell Vim to use folding by marker add the following lines to your If you need more information on this topic, read files <\/p>\n <\/a><\/p>\n One of Vim’s features that speeds up navigation is – marks. You can set a mark anywhere in the text and then quickly jump back to it. You can set several marks. You can set marks in several files and then quickly switch between them. I find myself set mark on the place I am currently working at with If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n All you need to do to have vertical indent display with pipe (“|”) character is to add the following two lines to your “ <\/p>\n <\/a><\/p>\n <\/p>\n <\/a><\/p>\n <\/p>\n <\/a><\/p>\n Save You will most likely notice that some color schemes do not change much colors in your console Try executing “ If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n Let’s download BlockComment.vim from http:\/\/www.vim.org\/scripts\/script.php?script_id=473<\/a> and copy it into <\/p>\n <\/a><\/p>\n There are, as usual, better (more convenient) ways to work with files and buffers. Vim website lists few plug-ins which can handle only files, or only buffers, or both at the same time. One of those plug-ins is winmanager by Srinath Avadhanula. Let’s grab winmanager from http:\/\/www.vim.org\/scripts\/script.php?script_id=95<\/a>.<\/p>\n Vim’s winmanager plug-in can make use of bufexplorer plug-in by jeff lanzarotta availalbe from http:\/\/www.vim.org\/scripts\/script.php?script_id=42<\/a>.<\/p>\n Installation is as usual – saving, unziping, and dos2unixing. Since we don’t want to always have file\/directory browser turned on, lets add a mapping line to our If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n One annoying thing that I find about taglist is that it resizes the terminal window when possible. I prefer to switch this feature off by add modifying my If you need more information on this topic, read file <\/p>\n <\/a><\/p>\n <\/p>\n <\/a><\/p>\n Embperl syntax highlighting plug-in is located at http:\/\/www.vim.org\/scripts\/script.php?script_id=61<\/a>. Download it and unzip it in your Embperl syntax highlighting plug-in uses it’s own color scheme, so don’t worry if you see colors different from the ones that you have expected.<\/p><\/blockquote>\n <\/p>\n <\/a><\/p>\nIntroduction<\/h2>\n
What is this document?<\/h3>\n
Who should read this document?<\/h3>\n
Prerequisites<\/h3>\n
.vimrc<\/code> configuration file.<\/p>\nStructure of the document<\/h3>\n
Methodology<\/h3>\n
.vimrc<\/code> configuration file and uses only the system-wide default file, which was not modified by me in any way. RedHat’s vim-6.1 version is installed on the server with no changes what-so-ever.<\/p>\n.vimrc<\/code> in \/home\/codemonkey\/<\/code> directory, which is a home directory for the “codemonkey” user. I have also created user specific Vim directory structure as follows:<\/p>\n[codemonkey@gucho codemonkey]$ # Which version of Vim is installed?\r\n[codemonkey@gucho codemonkey]$ rpm -qa | grep -i vim\r\nvim-minimal-6.1-18.7x.2\r\nvim-common-6.1-18.7x.2\r\nvim-enhanced-6.1-18.7x.2\r\n[codemonkey@gucho codemonkey]$ # In which directory am I now?\r\n[codemonkey@gucho codemonkey]$ pwd\r\n\/home\/codemonkey\r\n[codemonkey@gucho codemonkey]$ # User-specific Vim configuration\r\n[codemonkey@gucho codemonkey]$ touch .vimrc\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\/colors\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\/compiler\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\/doc\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\/ftplugin\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\/plugin\r\n[codemonkey@gucho codemonkey]$ mkdir .vim\/syntax<\/pre>\n
Additional help resources<\/h3>\n
\/usr\/share\/doc\/vim-common-6.1\/docs\/directory<\/code> (you path may vary slightly). I have put mentioned documentation files from this directory where appropriate.<\/p>\nBasic Configuration<\/h2>\n
Text wrapping<\/h3>\n
![\"Text](\"\/wordpress\/wp-content\/thumb-20040720-vim_text_wrapping.png\")
<\/a>As you code, sometimes text flows further than the width of the editor window. Some people like long lines to be wrapped (in other words, continued on the other line), while others prefer them unwrapped. You can configure Vim to behave according to your liking by adding “set wrap<\/code>” or “set nowrap<\/code>” to your .vimrc<\/code> configuration file.<\/p>\nFlexible tabs<\/h3>\n
set tabstop=4<\/code>” to your .vimrc<\/code> to display all occurrences of Tab character (ASCII #9) as 4 spaces. This option will not change the text, it will only change the displaying of the text.<\/p>\nset autoindent<\/code>” to your .vimrc<\/code> for Vim to automatically position the cursor with appropriate indentation level when you press Enter and want to write the next line of code. This is very useful when you are indenting your code in structures like loops and procedures.<\/p>\nset shiftwidth=4<\/code>” in your .vimrc<\/code> configuration file.<\/p>\nset wildchar=<\/code>” line in your .vimrc<\/code> file.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/indent.txt<\/code>.<\/p>\nLine numbering<\/h3>\n
![\"Line](\"\/wordpress\/wp-content\/thumb-20040510-vim_line_numbers.png\")
<\/a>While Vim always displays your current position in the status line, you might also want to see all lines numbered. To do that, you will need to add “set number<\/code>” to your .vimrc<\/code>.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/usr_03.txt<\/code>.<\/p>\nSyntax highlighting<\/h3>\n
![\"Highlighting](\"\/wordpress\/wp-content\/thumb-20040510-vim_syntax_light_bg.png\")
<\/a>The first thing any developer will notice in Vim is excellent syntax highlighting. All popular languages are supported. Syntax files for less popular are available from Vim web site. Perl is supported out of the box.<\/p>\n![\"Highlighting](\"\/wordpress\/wp-content\/thumb-20040510-vim_syntax_dark_bg.png\")
<\/a>Vim identifies keywords, comments, variables, strings, in-line POD and other standard parts of the program and highlights them. Vim supports two color modes: one for terminals with dark background color and another one for terminals with light background color. You can control these modes by specifying command “set bg=dark<\/code>” and “set bg=light<\/code>” in your .vimrc<\/code>.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/syntax.txt<\/code>.<\/p>\nText completion<\/h3>\n
Ctrl-n<\/code> \/ Ctrl-p<\/code> to cycle through the current word completion suggestions. Vim generates suggest list based on the words in the current file. If you need key completion to make suggestions from other files, then Vim by default understand the ctags<\/code> file. Simply run “ctags *.p?<\/code>” to generate ctags for all Perl files and modules in the current directory (assuming you are using “.pl<\/code>” extension for Perl scripts and “.pm<\/code>” extension for Perl modules). This Vim’s feature not only saves a tonne of time on typing, but greatly decreases the error rate, especially with long variable and procedure names in the code.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/usr_24.txt<\/code>.<\/p>\nWindow splitting<\/h3>\n
![\"Split](\"\/wordpress\/wp-content\/thumb-20040510-vim_window_split.png\")
<\/a>Sometimes I need to see two or more files simultaneously. While I can always start another Vim session in a separate terminal, it is not as comfortable at times as Vim’s window splitting feature.<\/p>\n:split<\/code>” while in the normal mode. To split current window vertically, use “:vsplit<\/code>” instead. If you don’t provide any filename as argument to split\/vsplit then current filename is used. You further split resulting windows as much as you like. Use Ctrl-w w<\/code> to cycle through the windows. “:close<\/code>” will close the current windows. “:only<\/code>” will close all windows except the current one.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/usr_08.txt<\/code>.<\/p>\nDiff mode<\/h3>\n
![\"Diff](\"\/wordpress\/wp-content\/thumb-20040510-vim_diff_mode.png\")
<\/a>Vim provides excellent facilities for checking and editing differences between two or more files. Execute “vimdiff main.pl main2.pl<\/code>” (or “vim -d main.pl main2.pl<\/code>“) from the command line to see difference made to file main.pl in file main2.pl.<\/p>\ndo<\/code> and dp<\/code> commands. do<\/code> will get the patch from the neighbor window and apply it to the current buffer, while dp<\/code> will apply the difference from the current buffer to the neighbor window.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/diff.txt<\/code>.<\/p>\nText folding<\/h3>\n
![\"Before](\"\/wordpress\/wp-content\/thumb-20040510-vim_folding_before.png\")
<\/a>![\"After](\"\/wordpress\/wp-content\/thumb-20040510-vim_folding_after.png\")
<\/a>Yet another popular feature found in popular editors and IDEs is text folding. I think that folding is easier shown then explained.<\/p>\n.vimrc<\/code>:<\/p>\n\" Folding configuration\r\nset foldmethod=marker\r\n\" Edit and uncomment next line if you want non-default marker\r\n\"set foldmarker=\"{{{,}}}\"<\/pre>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/usr_28.txt<\/code> and \/usr\/share\/doc\/vim-common-6.1\/docs\/fold.txt<\/code>.<\/p>\nMarks<\/h3>\n
mc<\/code> (m<\/code> is for “mark”, c<\/code> I use for “current”) and then quickly returning to the same place with 'c<\/code>.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/motion.txt<\/code>.<\/p>\nVertical Indent Display<\/h3>\n
![\"Vertical](\"\/wordpress\/wp-content\/thumb-20040510-vim_vertical_indent.png\")
<\/a>For some people indenting text horizontally is not enough. They need some kind of vertical indentation to help them see corresponding parts of the code. While I am not one of those people, I’ve seen this feature around so often that I decided to add it codemonkey’s .vimrc<\/code>.<\/p>\n.vimrc<\/code>.<\/p>\n\" This is for vertical indenting\r\nset list\r\nset listchars=tab:|\r\n\" NOTE the space char after last backslash.<\/pre>\n
:set list<\/code>” forces Vim to show hidden characters like tabulations, ends of lines, and ends of files. “:set listchars=tab:| <\/code>” asks Vim to show only tab characters and use a pipe (“|”) with a space (” “) to do so, instead of usual “^I” thing that Vim likes to show.<\/p>\nAdvanced Configuration<\/h2>\n
Common Configuration<\/h3>\n
Color schemes<\/h4>\n
![\"Colorscheme](\"\/wordpress\/wp-content\/thumb-20040510-vim_colorscheme_dante.png\")
<\/a>Let’s start simple. Vim website offers a handful of color schemes for all tastes and preferences. Finding and downloading these color schemes one by one can be a pain though. Luckily, world is not without kind people. Someone named Robert (MetaCosm) downloaded all color schemes and put them into a single archive file which he uploaded back to Vim’s web site. Let’s download it from http:\/\/www.vim.org\/scripts\/script.php?script_id=625<\/a>.<\/p>\ncolors.zip<\/code> in your .vim\/<\/code> directory and unzip<\/code> it. Making sure that all the files in UNIX format is also a good idea.<\/p>\n[codemonkey@gucho .vim]$ ls\r\ncolors.zip\r\n[codemonkey@gucho .vim]$ unzip colors.zip\r\nArchive: colors.zip\r\n creating: colors\/\r\n inflating: colors\/adaryn.vim\r\n inflating: colors\/adrian.vim\r\n inflating: colors\/aqua.vim\r\n inflating: colors\/astronaut.vim\r\n inflating: colors\/asu1dark.vim\r\n inflating: colors\/autumn.vim\r\n inflating: colors\/biogoo.vim\r\n inflating: colors\/blackdust.vim\r\n inflating: colors\/BlackSea.vim\r\n inflating: colors\/blue.vim\r\n inflating: colors\/bluegreen.vim\r\n inflating: colors\/bog.vim\r\n inflating: colors\/borland.vim\r\n inflating: colors\/breeze.vim\r\n inflating: colors\/brookstream.vim\r\n inflating: colors\/brown.vim\r\n inflating: colors\/bw.vim\r\n inflating: colors\/c.vim\r\n inflating: colors\/camo.vim\r\n inflating: colors\/candy.vim\r\n inflating: colors\/caramel.vim\r\n inflating: colors\/ChocolateLiquor.vim\r\n inflating: colors\/coffee.vim\r\n inflating: colors\/colorer.vim\r\n inflating: colors\/colorscheme_template.vim\r\n inflating: colors\/cool.vim\r\n inflating: colors\/dante.vim\r\n inflating: colors\/darkblue.vim\r\n inflating: colors\/darkdot.vim\r\n inflating: colors\/darkocean.vim\r\n inflating: colors\/darkslategray.vim\r\n inflating: colors\/dawn.vim\r\n inflating: colors\/default.vim\r\n inflating: colors\/denim.vim\r\n inflating: colors\/desert.vim\r\n inflating: colors\/elflord.vim\r\n inflating: colors\/emacs.vim\r\n inflating: colors\/evening.vim\r\n inflating: colors\/fine_blue.vim\r\n inflating: colors\/fnaqevan.vim\r\n inflating: colors\/fog.vim\r\n inflating: colors\/golden.vim\r\n inflating: colors\/ibmedit.vim\r\n inflating: colors\/ironman.vim\r\n inflating: colors\/koehler.vim\r\n inflating: colors\/lanzarotta.vim\r\n inflating: colors\/lilac.vim\r\n inflating: colors\/manxome.vim\r\n inflating: colors\/midnight.vim\r\n inflating: colors\/midnight2.vim\r\n inflating: colors\/morning.vim\r\n inflating: colors\/murphy.vim\r\n inflating: colors\/navajo-night.vim\r\n inflating: colors\/navajo.vim\r\n inflating: colors\/night.vim\r\n inflating: colors\/nightshimmer-theme.vim\r\n inflating: colors\/nightwish.vim\r\n inflating: colors\/northsky.vim\r\n inflating: colors\/oceanblack.vim\r\n inflating: colors\/oceandeep.vim\r\n inflating: colors\/pablo.vim\r\n inflating: colors\/PapayaWhip.vim\r\n inflating: colors\/peachpuff.vim\r\n inflating: colors\/potts.vim\r\n inflating: colors\/print_bw.vim\r\n inflating: colors\/rainbow_autumn.vim\r\n inflating: colors\/rainbow_breeze.vim\r\n inflating: colors\/rainbow_fine_blue.vim\r\n inflating: colors\/rainbow_fruit.vim\r\n inflating: colors\/rainbow_neon.vim\r\n inflating: colors\/rainbow_night.vim\r\n inflating: colors\/rainbow_sea.vim\r\n inflating: colors\/redblack.vim\r\n inflating: colors\/ron.vim\r\n inflating: colors\/sand.vim\r\n inflating: colors\/scite.vim\r\n inflating: colors\/sean.vim\r\n inflating: colors\/seashell.vim\r\n inflating: colors\/shine.vim\r\n inflating: colors\/taqua.vim\r\n inflating: colors\/tomatosoup.vim\r\n inflating: colors\/toothpik.vim\r\n inflating: colors\/torte.vim\r\n inflating: colors\/transparent.vim\r\n inflating: colors\/whitedust.vim\r\n inflating: colors\/wintersday.vim\r\n inflating: colors\/xemacs.vim\r\n inflating: colors\/xian.vim\r\n inflating: colors\/zellner.vim\r\n inflating: colors\/zenburn.vim\r\n[codemonkey@gucho .vim]$ dos2unix colors\/*\r\ndos2unix: converting file colors\/BlackSea.vim to UNIX format ...\r\ndos2unix: converting file colors\/ChocolateLiquor.vim to UNIX format ...\r\ndos2unix: converting file colors\/PapayaWhip.vim to UNIX format ...\r\ndos2unix: converting file colors\/adaryn.vim to UNIX format ...\r\ndos2unix: converting file colors\/adrian.vim to UNIX format ...\r\ndos2unix: converting file colors\/aqua.vim to UNIX format ...\r\ndos2unix: converting file colors\/astronaut.vim to UNIX format ...\r\ndos2unix: converting file colors\/asu1dark.vim to UNIX format ...\r\ndos2unix: converting file colors\/autumn.vim to UNIX format ...\r\ndos2unix: converting file colors\/biogoo.vim to UNIX format ...\r\ndos2unix: converting file colors\/blackdust.vim to UNIX format ...\r\ndos2unix: converting file colors\/blue.vim to UNIX format ...\r\ndos2unix: converting file colors\/bluegreen.vim to UNIX format ...\r\ndos2unix: converting file colors\/bog.vim to UNIX format ...\r\ndos2unix: converting file colors\/borland.vim to UNIX format ...\r\ndos2unix: converting file colors\/breeze.vim to UNIX format ...\r\ndos2unix: converting file colors\/brookstream.vim to UNIX format ...\r\ndos2unix: converting file colors\/brown.vim to UNIX format ...\r\ndos2unix: converting file colors\/bw.vim to UNIX format ...\r\ndos2unix: converting file colors\/c.vim to UNIX format ...\r\ndos2unix: converting file colors\/camo.vim to UNIX format ...\r\ndos2unix: converting file colors\/candy.vim to UNIX format ...\r\ndos2unix: converting file colors\/caramel.vim to UNIX format ...\r\ndos2unix: converting file colors\/coffee.vim to UNIX format ...\r\ndos2unix: converting file colors\/colorer.vim to UNIX format ...\r\ndos2unix: converting file colors\/colorscheme_template.vim to UNIX format ...\r\ndos2unix: converting file colors\/cool.vim to UNIX format ...\r\ndos2unix: converting file colors\/dante.vim to UNIX format ...\r\ndos2unix: converting file colors\/darkblue.vim to UNIX format ...\r\ndos2unix: converting file colors\/darkdot.vim to UNIX format ...\r\ndos2unix: converting file colors\/darkocean.vim to UNIX format ...\r\ndos2unix: converting file colors\/darkslategray.vim to UNIX format ...\r\ndos2unix: converting file colors\/dawn.vim to UNIX format ...\r\ndos2unix: converting file colors\/default.vim to UNIX format ...\r\ndos2unix: converting file colors\/denim.vim to UNIX format ...\r\ndos2unix: converting file colors\/desert.vim to UNIX format ...\r\ndos2unix: converting file colors\/elflord.vim to UNIX format ...\r\ndos2unix: converting file colors\/emacs.vim to UNIX format ...\r\ndos2unix: converting file colors\/evening.vim to UNIX format ...\r\ndos2unix: converting file colors\/fine_blue.vim to UNIX format ...\r\ndos2unix: converting file colors\/fnaqevan.vim to UNIX format ...\r\ndos2unix: converting file colors\/fog.vim to UNIX format ...\r\ndos2unix: converting file colors\/golden.vim to UNIX format ...\r\ndos2unix: converting file colors\/ibmedit.vim to UNIX format ...\r\ndos2unix: converting file colors\/ironman.vim to UNIX format ...\r\ndos2unix: converting file colors\/koehler.vim to UNIX format ...\r\ndos2unix: converting file colors\/lanzarotta.vim to UNIX format ...\r\ndos2unix: converting file colors\/lilac.vim to UNIX format ...\r\ndos2unix: converting file colors\/manxome.vim to UNIX format ...\r\ndos2unix: converting file colors\/midnight.vim to UNIX format ...\r\ndos2unix: converting file colors\/midnight2.vim to UNIX format ...\r\ndos2unix: converting file colors\/morning.vim to UNIX format ...\r\ndos2unix: converting file colors\/murphy.vim to UNIX format ...\r\ndos2unix: converting file colors\/navajo-night.vim to UNIX format ...\r\ndos2unix: converting file colors\/navajo.vim to UNIX format ...\r\ndos2unix: converting file colors\/night.vim to UNIX format ...\r\ndos2unix: converting file colors\/nightshimmer-theme.vim to UNIX format ...\r\ndos2unix: converting file colors\/nightwish.vim to UNIX format ...\r\ndos2unix: converting file colors\/northsky.vim to UNIX format ...\r\ndos2unix: converting file colors\/oceanblack.vim to UNIX format ...\r\ndos2unix: converting file colors\/oceandeep.vim to UNIX format ...\r\ndos2unix: converting file colors\/pablo.vim to UNIX format ...\r\ndos2unix: converting file colors\/peachpuff.vim to UNIX format ...\r\ndos2unix: converting file colors\/potts.vim to UNIX format ...\r\ndos2unix: converting file colors\/print_bw.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_autumn.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_breeze.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_fine_blue.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_fruit.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_neon.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_night.vim to UNIX format ...\r\ndos2unix: converting file colors\/rainbow_sea.vim to UNIX format ...\r\ndos2unix: converting file colors\/redblack.vim to UNIX format ...\r\ndos2unix: converting file colors\/ron.vim to UNIX format ...\r\ndos2unix: converting file colors\/sand.vim to UNIX format ...\r\ndos2unix: converting file colors\/scite.vim to UNIX format ...\r\ndos2unix: converting file colors\/sean.vim to UNIX format ...\r\ndos2unix: converting file colors\/seashell.vim to UNIX format ...\r\ndos2unix: converting file colors\/shine.vim to UNIX format ...\r\ndos2unix: converting file colors\/taqua.vim to UNIX format ...\r\ndos2unix: converting file colors\/tomatosoup.vim to UNIX format ...\r\ndos2unix: converting file colors\/toothpik.vim to UNIX format ...\r\ndos2unix: converting file colors\/torte.vim to UNIX format ...\r\ndos2unix: converting file colors\/transparent.vim to UNIX format ...\r\ndos2unix: converting file colors\/whitedust.vim to UNIX format ...\r\ndos2unix: converting file colors\/wintersday.vim to UNIX format ...\r\ndos2unix: converting file colors\/xemacs.vim to UNIX format ...\r\ndos2unix: converting file colors\/xian.vim to UNIX format ...\r\ndos2unix: converting file colors\/zellner.vim to UNIX format ...\r\ndos2unix: converting file colors\/zenburn.vim to UNIX format ...\r\n[codemonkey@gucho .vim]$<\/pre>\n
\n
vim and gvim color schemes<\/h3>\n
vim<\/code>. That is because they are most probably designed for GUI version of Vim, called gvim<\/code>.<\/p>\ngvim +'colorscheme peachpuff' main.pl<\/code>” to see how gvim looks with selected color scheme.<\/p><\/blockquote>\n![\"Colorscheme](\"\/wordpress\/wp-content\/thumb-20040510-vim_colorscheme_nightwish.png\")
<\/a>Now you can try all those color schemes one by one with “:colorscheme something<\/code>” and choose the one you like best. When you are done choosing, add line “colorscheme something<\/code>” to your .vimrc<\/code>.<\/p>\n\/usr\/share\/doc\/vim-common-6.1\/docs\/usr_06.txt<\/code>.<\/p>\nBlock commenting<\/h3>\n
![\"Block](\"\/wordpress\/wp-content\/thumb-20040510-vim_blockcomment.png\")
<\/a>It is an often need to comment or uncomment blocks of code during the development cycle. While there is a way to do it in Vim without any additional configuration, I try to make life as easy as possible and install the BlockComment plug-in by Chris Russell.<\/p>\n.vim\/plugin\/<\/code> directory. This plug-in automatically provides us with two mappings: “.c<\/code>” for commenting code and “.C<\/code>” for uncommenting code back.<\/p>\nFile and buffer browser<\/h3>\n
![\"Winmanager\"](\"\/wordpress\/wp-content\/thumb-20040510-vim_winmanager.png\")
<\/a>Vim supports editing of several files simultaneously. One can start Vim as “vim main.pl main2.pl<\/code>” and then use “:next<\/code>” and “:previous<\/code>” to navigate through open files (called “buffers”). It is also possible to open files for editing without quiting Vim every time. For that, one should use simple “:e main2.pl<\/code>” command, where main2.pl is the name of needed file.<\/p>\n.vimrc<\/code> to “:WMToggle<\/code>” by F2<\/code>.<\/p>\n\" This is for winmanager\r\nmap <F2> :WMToggle<CR><\/pre>\n
\/usr\/share\/doc\/vim-common-6.1\/docs\/usr_23.txt<\/code>.<\/p>\nTag explorer<\/h2>\n
![\"Tag](\"\/wordpress\/wp-content\/thumb-20040510-vim_taglist.png\")
<\/a>If you ask me, I am almost happy. The last thing that I am missing is something that will ease up my code browsing. I need a fast way of switching between different parts of my code and hierarchical view of it. Once again I go fishing to Vim web site and get myself a nice looking taglist plug-in by Yegappan Lakshmanan from http:\/\/www.vim.org\/scripts\/script.php?script_id=273<\/a>. This one is not even an archive! You just need to copy it into your .vim\/plug-in<\/code> directory. Let’s map “:Tlist<\/code>” command to F3<\/code> key.<\/p>\n\" This is for taglist\r\nmap <F3> :Tlist<CR><\/pre>\n
.vimrc<\/code> in the following way.<\/p>\n\" This is for taglist\r\nlet Tlist_Inc_Winwidth = 0\r\nmap <F3> :Tlist<CR><\/pre>\n
\/usr\/share\/doc\/vim-common-6.1\/docs\/tagsrch.txt<\/code>.<\/p>\nPerl-Specific Configuration<\/h2>\n
Embperl syntax highlighting<\/h3>\n
![\"Highlighting](\"\/wordpress\/wp-content\/thumb-20040510-vim_syntax_embperl.png\")
<\/a>If you use Embperl perl module for developing dynamic content websites, then you will need to download Embperl syntax highlighting plug-in developed by Lukas Zapletal. These steps are similar for setting up highlighting for any other programming language that you might use and which is not supported out of the box.<\/p>\n.vim\/<\/code> directory. Again, passing all new files through dos2unix is a good idea, if you are on a UNIX\/Linux box as I am. vimrc_example<\/code> shipped with the archive contains the example of configuration that you’ll need to put into your .vimrc<\/code>.<\/p>\n[codemonkey@gucho .vim]$ ls\r\ncolors colors.zip Embperl_Syntax.zip\r\n[codemonkey@gucho .vim]$ unzip Embperl_Syntax.zip\r\nArchive: Embperl_Syntax.zip\r\n inflating: colors\/embperl_yellow.vim\r\n creating: syntax\/\r\n inflating: syntax\/embperl.vim\r\n inflating: vimrc_example\r\n[codemonkey@gucho .vim]$ cat vimrc_example\r\n\"let perl_fold=1\r\naugroup filetypedetect\r\nautocmd! BufNewFile,BufRead *.epl,*.phtml setf embperl\r\naugroup END\r\nautocmd BufNewFile,BufRead *.epl,*.phtml colorscheme embperl_yellow<\/pre>\n
\n
Embperl color scheme<\/h3>\n
Perl syntax compiler<\/h3>\n
![\"Perl](\"\/wordpress\/wp-content\/thumb-20040510-vim_perl_compiler.png\")
<\/a> Most of Integrated Development Environments (IDE) try to simplify write-compile-debug cycle. One of the things which can make the cycle easier is automatic cursor positioning to the place in the code where error occurred. Vim can do this for almost any language and compiler. If you know the format that your compiler spits out, then you can configure Vim to parse those errors and position the cursor for you. Since I am not the first Perl developer who uses Vim, I assumed that someone already wrote the compiler error syntax parser (sounds horrifying, isn’t it?).<\/p>\n
![](\"\/wordpress\/wp-content\/20040510-vim_perldoc.png\"){kind=link}