![]() I think I tried it for the first time in about 2003, and quickly gave up. However, I have decided that the advantages of redefining the Tab key in this way outweigh the disadvantages.I have been using Vim for most editing for about 12 years now. It has taken me a while to learn not to use the Tab key to enter TAB characters but to use CTRL-Tab instead. Note also that manpageview is being used to view the manpage for the CPAN module. The example shows a Perl script where the choice being made from the list offered by Supertab is uptodate. Provides insert completion functionality using the Tab key. I find the menu in gVim more useful myself. The image shows gVim with the tag list in a window. I believe that most Linux distributions ship with this utility, but if not it seems to be easily available in repositories. The plugin makes us of the Exuberant Ctags utility to index tags in a source file. The list is in a window in Vim or in a menu in gVim. This plugin provides source code browsing by listing tags (functions, classes, structures, variables, etc.). The image shows the result of the :Gstatus command which is equivalent to typing git status on the command line. My $str = *whee! vlllls' my $str = 'whee!' "Look ma, I'm *HTML!" cs" Look ma, I'm HTML! An asterisk (*) is used to denote the cursor The following extract from the Help text should make this clearer: Consider the following examples. The plugin provides mappings to easily delete, change and add "surroundings" such as quotes, braces and parentheses. This is a great way to view man pages, with the ability to search and cut and paste the contents. ![]() This is a man page viewer for use within Vim. If you are a C or C++ programmer Fritz Mehner also provides a plugin for these languages here. Note the lower window showing the various problems detected by perlcritic. Perltidy will reformat your Perl script, and Perlcritic will critique it according to the rules based on Damian Conway's book Perl Best Practices. Two of the functions I find particularly useful are perltidy and perlcritic. You can also get regular expression help, check, run and debug the script As with the Bash plugin from the same author I find it most useful from gVim where the menus can be used to perform a wide range of actions.Īgain, you can use it to insert statements, boilerplate text and comments, in a similar way to the Bash plugin. This plugin provides a Perl scripting IDE for Vim and gVim. It's an amazingly detailed package that's well worth dedicating the time to learn if you often write Bash scripts. The plugin can be used from the menu or by typing short-cut sequences such as \ct which inserts the current date and time at the cursor position. Improve speed and comfort when writing shell scripts. There are many additional hints and options which can Syntax checking, running a script, starting a debugger can be done This is done by inserting complete statements, comments, idioms, and code I find it most usable in gVim where it offers a comprehensive set of menus which you can see in the example.įrom the Help text: It is written to considerably speed up writing code in a consistent style. This one provides a Bash scripting IDE for Vim and gVim. To achieve this I have the following in my ~/.vimrc " NERDTree settings (only in GUI mode) I prefer to use NERDTree in gVim and not in Vim. ![]() Type :h NERD_tree for the large and comprehensive help file. In case you're interested, the colour theme I use in gVim is "Murphy". A tree is displayed in a window which can be scrolled and traversed to find files to edit. A particular directory is opened by typing :NERDTree somedir. This plugin provides a file browser within Vim/gVim. If you have never made enhancements to this editor, here's a site with a very good tutorial on how to install plugins. In these notes I have listed some of the plugins I use to enhance Vim and gVim's functionality. I don't remember when I changed to Vim, but for many years I have used it (actually gVim) as an IDE (Integrated Development Environment), particularly for writing Bash and Perl scripts. Learning Emacs didn't seem like a good choice since it wasn't usually available on the systems I was administering. In those days you could usually count on a system having vi (or at a pinch, when the system would only boot into single user mode, ed). I started learning vi a long time ago when I first encountered Unix systems. Summary: Some of the Vim/gVim plugins I use and would like to recommend
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |