On 2007-05-17 at 20:38 +0000, Zach White wrote: > I can't stand color syntax highlighting, myself. Every time I try to use > it I get distracted by the changing colors every time I open or close some > quoting method. And don't get me started on the problems when the file-type > auto-detection fails and it tries to highlight your python file using some > C-like syntax.
I'm annoyed that there's no multi-editor type-marking that's actually used by all the mainstream editors. -*- python-mode -*- (or whatever it is), vs: vim: set filetype=python : , etc. If I'm wrong, please help me minimise the hate and let me start setting file type, tab settings etc in one place, out of the way at the bottom of the file, in a way which won't break just because someone uses a different format. > -Zach (Who's still upset that there's no way he can use nvi's multi-level > undo model when stuck in vim) Please elucidate; how does this differ from undolists? help undo-branches or undo-tree .. Thanks, -Phil
