" Set settings
set autoindent
set title
set ruler
set nocompatible
set showcmd
set ts=4
set tw=72
set backspace=indent,eol,start
set incsearch
syntax on

" Remember where I last edited a file
set viminfo='10,"100,:20,%,n~/.viminfo
au BufReadPost * if line("'"") > 0|if line("'"") < = line("$")|exe("norm '"")|else|exe "norm $"|endif|endif

if &term =~ "xterm-debian" || &term =~ "xterm-xfree86"
set t_Co=16
set t_Sf=^[[3%dm
set t_Sb=^[[4%dm
" Settings set

" Map mappings
:inoremap ( ()i
:inoremap [ []i
:inoremap " ""i
:inoremap { {}i
:inoremap < <>i

map W :!aspell -c -x %
map F gqap

" make an element out of anything you type with a CR in the middle
imap ,,, bdwapakA

" Fix common typos
iab teh the
iab hte the
iab adn and
iab taht that
iab htat that
iab fo of
iab ot to
" Mapping mapped

if has("autocmd")
" Enabled file type detection
" Use the default filetype settings. If you also want to load indent files
" to automatically do language-dependent indenting add 'indent' as well.
filetype plugin on
endif " has ("autocmd")


A while back I was using CVS to synchronize and version my school work, and I was looking for a method of writing papers so the working files were text instead of binary allowing diffs to be generated via CVS. That lead me to LaTeX, and it worked out all right. I found that I was quite happily able to generate my text in vim, version it with CVS and generate a final PDF, the only binary format in the whole process.

Now, well after I really could have used it, this article pops up. It is a useful primer, but it doesn’t really touch on the one things that will probably bite a lot of users in the ass – there are zillions of versions of LaTeX and its packages, and so you’ll have to experiment to find out what works on your system. Still, it’s a good document preparation system, and I’m glad to know something about how it works.