[OPEN-ILS-DEV] [PATCH] Renewal notice hook, cleanup

[Jason Etheridge]

> Also, some other projects that I've worked on have had a rule (informal
> in some cases, more formal in others - hello PHP / PEAR!) that white
> space changes should be committed separately from code changes, to make
> it simpler for other people to focus on the actual code diffs. I don't
> think we have any such rules (informal or formal) about that in
> Evergreen today, but it does make sense to me. Anyone else care to weigh
> in?

That's how I've been trying to do it, but of course, if I change
whitespace by accident, I'm too lazy to try to work it out of my
commit. :)

The .vimrc I tend to use looks like this (I think our expandtab is different?):

set hlsearch
set tabstop=4
set softtabstop=4
set shiftwidth=4
vnoremap < <gv
vnoremap > >gv
set nobk
set whichwrap=b,s,<,>,[,]
set backspace=indent,eol,start
set smartcase
filetype on
syntax enable
set expandtab
autocmd BufEnter ?akefile* set noet ts=4 sw=4  "use real tabs in Makefiles
autocmd BufEnter *txt set noet ts=4 sw=4  "use real tabs in txt files
autocmd BufEnter *out set noet ts=4 sw=4  "use real tabs in txt files
autocmd BufEnter *csv set noet ts=4 sw=4  "use real tabs in txt files
au BufNewFile,BufRead *.xhtml setf html
au BufNewFile,BufRead *.bsh setf java
au BufNewFile,BufRead *.ftl setf html
set bg=dark
let loaded_matchparen = 1

I have this sitting at http://evergreen-ils.org/~phasefx/.vimrc to
make it easy whenever I find myself in a new environment.

-- 
Jason Etheridge
 | VP, Tactical Development
 | Equinox Software, Inc. / The Evergreen Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  jason at esilibrary.com
 | web:  http://www.esilibrary.com