Skip to main content

Vim: More Vim Tidbits

I reread "vimtutor" for the first time in years. I learned a few things:
e
"e" is a motion that means "to the end of the word". "ce" is useful.

/searchterm<enter>nN
When searching, "n" to search forward, "N" to go backwards. Start with "?" to aways go backwards. I had forgotten about "N".

:#,#s/old/new/g
Do a search and replace only between two line numbers.

:%s/old/new/gc
Do a search and replace with prompts.

:r !shellcommand
Execute a shell command and insert the results at the cursor.

R
This is over-write mode.

partial-command^D<tab>
Show possible command completions, then tab to complete.

evim
gvim in "easy" mode.
In the Vim tutorial, there's a mention of "$VIMRUNTIME/vimrc_example.vim" which I had never seen before. This helped me to improve my own .vimrc:
" These are general settings.
colorscheme torte
set autoindent
set guifont=Monospace\ 9
set hlsearch
set incsearch
set ruler
set showcmd

" Allow backspacing over everything in insert mode.
set backspace=indent,eol,start

" "T" toggles the taglist for ctags.
map T :TlistToggle<CR>

" Enable file type detection. Use the default filetype settings, so that
" mail gets 'tw' set to 72, 'cindent' is on in C files, etc. Also load
" indent files, to automatically do language-dependent indenting.
syntax on
filetype plugin indent on

" Put these in an autocmd group, so that we can delete them easily.
augroup vimrc
au!
autocmd FileType css setlocal sw=4 sts=4 et
autocmd FileType html setlocal sw=2 sts=2 et
autocmd FileType java setlocal sw=4 sts=4 et
autocmd FileType javascript setlocal sw=4 sts=4 et
autocmd FileType mason setlocal sw=2 sts=2 et
autocmd FileType ocaml setlocal sw=2 sts=2 et
autocmd FileType php setlocal sw=2 sts=2 et
autocmd FileType perl setlocal sw=4 sts=4 et
autocmd FileType python setlocal sw=4 sts=4 et tw=72
autocmd FileType scheme setlocal sw=2 sts=2 et
autocmd FileType sql setlocal et
autocmd FileType htmlcheetah setlocal sw=2 sts=2 et
autocmd FileType text setlocal sw=2 sts=2 et tw=79
augroup END
Now that I know how to turn on intelligent indentation *and* still control it on a per-language basis, I'm even happier :)

Comments

Anonymous said…
I've been using Vim for over 10 years and didn't know about the 'N' on searches. Thanks!
jjinux said…
Awesome!
Wonderful! Thanks for the tips.

I got two things from this set of tips that will really help me. Two things that have been bugging me for ages that I always do.

The highlight search... which used to be on with vim 6.x, also the shell command insert.

I use the shell command insert now for quickly inserting the date into my log files that I keep for every project. Now no more typing into the shell, and copy/pasting it.

:r !date

Thanks again!
wam said…
You said Start with "?" to aways go backwards. Actually, if you start a query with "?", then go on to the next match with 'n' you will continue to search backwards; however, if you go to next search result with 'N', you will search backwards from you search's initial direction, thus searching forwards.

As far as using :r !shellcommand, I personally use !!shellcommand which replaces current line with the shell command's output.

Also, a good alternative to R for replacing text (e.g. "write over mode") is c[motion/distance] to change only the specified amount of text. For example, to change the current line 'cc' To change just 3 words 'c3w' To change text to a pattern 'c/pattern'
Anonymous said…
set guifont=Bitstream\ Vera\ Sans\ Mono\ 14
Anonymous said…
That rocks. There were a few tips here I didn't know. I think I need to put "vim tutorial" on my list of things to do... I bet there are a few more tips I still need to learn. =)

Glen

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p