de cuts everything from, and including, the character under the cursor up to, and including, the last character of the world, e is an inclusive motion. dw cuts everything from, and including, the character under the cursor up to, and excluding, the next word, w is an exclusive motion. The answer to your question is … Read more
In command mode (where you are when you hit : in normal mode), you can do ctrl-R /, which will expand to your last search term (other ctrl-R favorites are ” for your yank buffer, or % for the full path of the current window) You actually don’t need to do that though. If you … Read more
Make use of modeline. Put the following line: // vim: set ft=javascript: more info about vim’s modeline.
This behavior is normal. Vim’s default is not to remember which code you had folded vs. unfolded from one session to the next. You can save your current folds; when you finish editing a file, before exiting vim, enter the command :mkview. When you next open the file, if you enter :loadview, it will restore … Read more
From the terminal If you have the mvim script installed (it is in the dmg, just put it somewhere in your PATH), you can just type in a shell: mvim -d file1 file2 You can alias this to mvimdiff if you like. From within macvim In macvim, like in vim , you can also use: … Read more
This works for me: :s/\s\+/ /g
:belowright split will open the new window on the bottom regardless of whether or not you have set splitbelow. Similarly, :aboveleft split will open the new window at the top regardless of the ‘splitbelow’ setting.
If you have the setting set clipboard=unnamedplus in your .vimrc then this will not be working. For OSX you have to use set clipboard=unnamed For Linux you will probably need to use set clipboard=unnamedplus Heres the snippet from my personal .vimrc if system(‘uname -s’) == “Darwin\n” set clipboard=unnamed “OSX else set clipboard=unnamedplus “Linux endif
Vim and versions The big problem with you question is, that this question depends on the vim version. By vim version I mean not the version (7.3…), but much more if you’re using MacVim, gVim, the terminal edition, etc. The version is imporant, because the t_vb param (type :set t_vb? to get it) is different … Read more
A bit old, but I’ve just found this on reddit: You can start vim with the -w flag to write all keystrokes in a file. See :h -w vim -w filename