Comment by valbaca | Hacker News Reader

Comment by valbaca | Hacker News Reader

Quick renaming of variables: what to type"explanation

    gd" go to definition of variable
    :%s/" beginning of a replace...
    Ctrl-r /" inserts the last word searched into the command, so what "gd" found
    /newname/gc" finish the replace command, g=global replace, c=confirm each replace

Save a character going to a line: instead of using :42<enter> to go to line 42, can use 42G

Auto-indent: =

Go to last file: Ctrl-^

Abbreviations: put this in your ~/.vimrc

    iab cmain int main() {
    \<CR>    return 0;
    \<CR>}

Insert the contents of a file: :r <filename>

I like to have a ~/gitmessage.txt which has a template I like, then when I do git commit all I have to do is:

    :r ~/gitmessage.txt

Vim + Ctags:

Ctags link usages and definitions so you can navigate through code like in an IDE without the bloat of an IDE. Works best with C, but works pretty well with any language with C-like syntax (and more).

Goto tag (definition) of what's under cursor: Ctrl-]

Go back: Ctrl-t

Open tag in a preview: Ctrl-w

:tag <tag> " go to tag, like:

    :tag someFunction
    :tag SOME_CONSTANT

> Insert the contents of a file: :r <filename>

The file name can be a pipe instead.

Let’s say you have a Makefile based project and the dependencies aren’t as complete as they ought to be. With your cursor on this line in the Makefile:

    SOURCES = \

You can say

    :r !ls src/*.c

That will put the complete list of extant C source files into the file at that position, complete with the “src/“ path prefix. Then to format the list properly for “make” syntax, use Shift-V to select the list, hit the right angle bracket (“>”) once to indent it a level, then say:

     :s/$/ \/

This trick of replacing the start (“^”) or end (“$”) of a line is very often helpful. Here I’ve used it to ask Vim to put a space and backslash after every line to allow the SOURCES variable definition to continue from one line to the next.

(This will look like “:’<,’>s...” in your editor, with the bit between the colon and s being inserted by Vim; it means “front the start of the selection to the end.”)

Remove the final backslash and it’s done.

The advantage of working this way is that you aren’t manually transcribing things the computer already knows and can report on command.

The possibilities here are vast. For instance, if your C source files are buried under subdirectories of `src`, say this instead:

    :r !find src -name \*.c

Reply on news.ycombinator.com