freebsd.munk.me.uk - Vim

Move Quicker In Vim!

nospam@example.com (munk) — Tue, 26 Sep 2006 16:11:00 +0000

Here's a list of my fav keyboard shortcuts for moving around Vim rapidly. There are an infinite number of other great keyboard shortcuts in Vim, these are just the ones I use most and that come to mind right now for zipping around quickly. As you read this, fire up Vim and try them out :)

Feel free to point out any that I've missed out in the comments!

gg - goto the first line of the current document.

G - goto the last line of the current document

* - * is a great shortcut, it finds the next occurence of the word your cursor is currently on. The '#' key does the same but backwards through the current document, though I have # mapped to auto comment blocks of code/script.

'a and ma - using the keystroke 'a will set a 'mark' named 'a' in the document at the current line you're at. Hitting the ma keystroke will take you back to the mark / line named 'a'. You can do the same with any letters in the range [a-zA-Z], just substituate a for the letter you want (mb mc md, 'b 'c 'd to mark/goto marks b, c or d).

% - whilst on a bracket/brace, goto the matching bracket/brace - useful if you're coding/scripting and you want to check if your brackets are closed properly.

Vim 7 New Features

nospam@example.com (munk) — Wed, 20 Sep 2006 21:21:00 +0000

Vim 7 has been out for a while now and I've not commented on it as yet. There's an article about the new changes in Vim 7 I was reading and thought I'd make some comments on the features I like/dislike about Vim7.

Highlighting Matching Parentheses
Bracket Highlighting is a useful feature for programmers - when your cursor is over a bracket, the corresponding bracket is auto highlighted for you so you can easily check a brace is closed properly.

However, personally I find it slows down Vim way too much if you're editing code that has many nested brackets in - Vim takes a long time to move from one line to the next when you're hitting 'j' or 'k' to move down/up through lines. Ok it's only a split second difference, but you do get that kind of juddery movement (imagine editing in vim over a 56k modem line whilst downloading something else!). Not for me thanks - I resorted to turning the feature off.

For anyone who wants to turn parenthesis automatching off in Vim 7 without having to trawl through the manual, add this to ~/.vimrc:

CODE:

:let loaded_matchparen = 1

It's in the online help pages for ':help matchparen' if you want to read up on it.

Undo Branches
Vim 7's undo branches feature lets you revert your changes to a time in the past when everything was good and dandy. Not only that but it can deal with undo branches - when you make a change, undo it, then make another change... vim now allows you to go back to the first change you made (if I understand it correctly).

Now to be honest this sounded like a really good feature to me, but so far I've not screwed up enough to have to work out how to browse through the different undo branches. I can imagine if I spent an hour working on a document only to realize I needed something I'd changed half an hour ago, and that change wasn't in the direct history I could go back to using 'u' for undo... then ok maybe I'd take the time to read the docs about how to find the right undo branch to restore the text I was missing. But that's not come up yet. :o Sounds good though.

There are some other features I've not tested out as yet - omni completion sounds useful, like syntax autocompletion by the sounds of it. Start typing in a function name in php or a tag in html, hit 'ctrl-x ctrl-o' in command mode and you get up a list of possible completions for the text you've started entering. I might give this a go next time I use it, will have to see.

Vim Tips: Open Files Quicker In Vim

nospam@example.com (munk) — Mon, 11 Sep 2006 23:34:17 +0000

This tip allows you to open files easily / quickly in the same directory as the file you're currently working on in Vim. By default, Vim opens files from the current working directory when you hit ':e' which is annoying if you want to quickly open a file in the same directory as the file you're working on without having to drill down through lots of subdirectories. Using this key mapping tip though you can open files from the working directory of the file you're currently working on by hitting ',e'.

The tip includes an example, it's really worth trying if you use Vim as your main editor - personally I'd find it hard working without it in Vim now.

First of all it's worth noting that there is a Vim setting that allows you to have the working directory follow the file you're currently working on:

CODE:

# Add this to ~/.vimrc to make it permanent:
:set autochdir

However the following is still relevant because it's not always the case you want this behaviour and the keystroke ',e' is as quick as ':e' to type anyway to get this equivalent functionality to work.

Here goes with the ',e' mapping:

Add the following key mapping to ~/.vimrc:

CODE:
map ,e :e <C-R>=expand("%:p:h") . "/" <CR>

Save the ~/.vimrc file.
Read in the new mapping by sourcing the ~/.vimrc:

CODE:
:source ~/.vimrc

or just exit and restart vim.

Now the ',e' mapping should work. To test it:

Open a file NOT in the current working directory:

CODE:

# (this is in Vim):
# /root is my current working directory
:!echo $PWD
/root
# open up a file in another directory:
:e /var/log/messages
# now try the new key mapping - when you hit the key stroke ',e' you get:
:e /var/log/
# hitting <TAB> allows autocompletion on all files in /var/log as well :)

I should give credit where it's due though, I found this tip on the Vim Tips site - always worth searching through if you ever need to get something done in Vim. Easier still, download all of the Vim Tips submitted on the site, then just search for the keywords that you're looking for a tip on (searching in it for ',e' I just found out the tip above was tip #2 (of 1327!!!)). Credit goes to those guys in tip #2 for the above. :)

Mmm... just reading through those comments I'm not sure if I'll bother posting this article, seems there's an even easier way to have the working dir follow the current file using ':set autochdir'... ack and I'm so used to using ,e now... then again though there are some times when you don't always want that autochangedir functionality. Ho hum I'll stick with ',e' I think.

Vim Tips: Comment Out Code With One Keystroke

nospam@example.com (munk) — Fri, 08 Sep 2006 16:10:58 +0000

When coding/scripting in Vim it's useful to be able to comment out one or more lines quickly and easily. The following code snippet allows you to comment out either the current line (in command mode) or all the highlighted lines (in visual mode) using the '#' key - add it to your ~/.vimrc file to have it load when vim starts:

CODE:

" comments mapping
map # :s/^/# /<cr>j
vmap # :s/^/# /<cr>gv

Of course this knocks out the default functionality of the # key - search for word nearest cursor backwards (you can get similar functionality by hitting *, then 'N').

Vim Shell - is there any reason to use a full login shell again?

nospam@example.com (munk) — Sun, 21 Mar 2004 13:05:08 +0000

Ok perhaps it's wishful thinking that I'd never need to switch endlessly back and forth between a login shell and vim again, but after finding the promising vimsh vim script I did think I could be on the way to living my server admin life completely in vim.

The script is very interesting - after sourcing the script from within vim you essentially get a login shell within a new vim buffer. Unlike a regular login shell though, with vimsh you get the added bonus that you can move around the shell buffer as you would in a regular vim buffer and yank/paste lines as you want. This could be very useful for writing up articles that include a lot of shell snippets - this site has it's fair share of those :P

vimsh is written by Brian Sturk - he has a page detailing his contributions to vim here