Re: switching to vim-tiny for standard vi?

[Louis-David Mitterrand]

On Tue, Dec 20, 2005 at 01:53:07PM -0600, Steve Greenland wrote:
> On 20-Dec-05, 12:54 (CST), Graham Wilson <[EMAIL PROTECTED]> wrote: 
> > I've found vim's defaults are unreadable except on a white background,
> > since that is what vim assumes you have by default.
> 
> Actually, I do use a white background. Apparently your tolerance for
> yellow on white is higher than mine. (Not meant sarcastically, it's
> quite possible that you do see that combo better than I do.)

FWIW I have been using this for years on a white background and it's
much more readable: 

if &background == "dark"
  hi Commentterm=bold ctermfg=Cyan guifg=#80a0ff
  hi Constant   term=underline ctermfg=Magenta guifg=#ffa0a0
  hi Specialterm=bold ctermfg=LightRed guifg=Orange
  hi Identifier term=underline cterm=bold ctermfg=Cyan guifg=#40
  hi Statement  term=bold ctermfg=Yellow guifg=#60 gui=bold
  hi PreProcterm=underline ctermfg=LightBlue guifg=#ff80ff
  hi Type   term=underline ctermfg=LightGreen guifg=#60ff60 gui=bold
  hi Ignore ctermfg=black guifg=bg
else
  hi Commentterm=bold ctermfg=DarkCyan guifg=Blue
  hi Constant   term=underline ctermfg=DarkBlue guifg=Magenta
  hi Specialterm=bold ctermfg=DarkRed guifg=SlateBlue
  hi Identifier term=underline ctermfg=DarkGreen guifg=DarkCyan
"   hi Statementterm=bold ctermfg=DarkMagenta gui=bold 
guifg=Brown
  hi Statement  term=bold ctermfg=DarkMagenta guifg=Brown
  hi PreProcterm=underline ctermfg=Brown guifg=Purple
"   hi Type term=underline ctermfg=DarkGreen guifg=SeaGreen gui=bold
  hi Type   term=underline ctermfg=DarkGreen guifg=SeaGreen 
  hi Ignore ctermfg=white guifg=bg
endif
hi Error term=reverse ctermbg=Red ctermfg=White guibg=Red guifg=White
hi Todo  term=standout ctermbg=Yellow ctermfg=Black guifg=Blue 
guibg=Yellow

highlight link Typedef Special
highlight link StorageClass Special

Insert in ~/.vim/syntax.vim and make sure your ~/.vimrc has:

if has("syntax")
let mysyntaxfile = "~/.vim/syntax.vim"
let myscriptsfile = "~/.vim/scripts.vim"
let myfiletypefile = "~/.vim/filetype.vim"
syntax on
endif

-- 
Typed slowly for those who cannot read fast.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel source 2.4.22 and ipvs problems

[Louis-David Mitterrand]

On Mon, Oct 06, 2003 at 07:12:03PM +1000, Herbert Xu wrote:
> Bao C. Ha <[EMAIL PROTECTED]> wrote:
> > 
> > I am trying to patch the kernel 2.4.22 and got into troubles.  It seems
> > that the Debian kernel has been patched to do away the pmtu field of
> > the struct dst_entry (include/net/dst.h).
> > 
> > Any sugegstions on how to get it working again.  The last working Debian 
> > kernel with IPVS is 2.4.20.
> 
> You can either use a vanilla kernel, or unapply the IPSEC patch as
> documented in the README.Debian file.

Why is the ipsec patch applied by default in the debian kernel? Asking
users to unapply a patch that shouldn't be in the stable kernel in the
first place is unacceptable. Telling them to use the "vanilla kernel"
makes them lose the security updates, the only ones that should be
applied to debian's kernel-source packages.

This whole thing is a unintuitive mess that has certainly caused more
aggravation than benefited anyone. How was the old system of having a
separate ipsec patch broken?

-- 
They can have my jeans, as soon as they pry them off my dead, cold ass.
-- (Spackler on /. about corporate dress code becoming formal again)