Package: vim-vimoutliner
Version: 0.3.4-8
Severity: wishlist
OK, so the real bug here was that I had never really used vim in colour,
and so had not noticed that it was universally assuming that TERM=xterm
means black-on-white text.
Perhaps vim colour detection can somehow be improved, or perhaps it would
be nice if everyone could agree that terminals doing dark backgrounds
define TERM=xterm-dark and then we can wait for the world's remote
computers to start supporting that without falling in a heap when they
see an unsupported terminal, but in the mean time:
If you're a total vimoutliner newbie (as am I) and whenever you start
vim on an empty outline file you just get a black screen, and then get
to type in black it takes a while to notice that TAB turns the lights on.
Actually, going back a step, I seem to remember initially wondering
what I had to do to load vimoutliner at all after I'd installed it, so a
mention of the fact that it pops up automatically if the file extension
is right in the README might be nice too.
Then we get to the attempt to fix the problem. Eventually, I realised
that what I actually wanted was nothing to do with vimoutliner, but
rather that adding something like:
if &term == "xterm"
set background=dark
endif
But on my travels to get there, the README.Debian for this package
pointed me in the direction of /etc/vim/vimoutlinerrc where I found a
commented out:
colorscheme vo_dark
I tried this at the : prompt in vim, and it worked, so I uncommitted it.
That doesn't help, since it seems that there is nothing actually looking
at vimoutlinerrc -- it works if I explicitly source it in my vimrc,
but I see no mention of a need to do that in this package's readme,
so I'm wondering if there's a but in that it's supposed to somehow
automatically load that file as the README.Debian implies.
Oh, and if it makes any difference, I tried installing vimoutliner with
vim-addons, but that didn't make it look at the vimoutlinerrc either.
So, how to fix this?
Well, a mention the README.Debian of the fact that if you get
black-on-black text it's because you need to set background=dark would
have saved many hours, but I'd understand if you thought that this would
clutter the README.
A colorscheme that didn't start with black (dark grey perhaps) would
have also been helpful.
A note in the vimoutlinerrc describing what you need to do to make it
active would be very useful. And a note in the same file next to the
colorschemes saying that you should perhaps fix the background setting
rather than the colorscheme would also be handy.
Cheers, Phil.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages vim-vimoutliner depends on:
ii libpalm-perl 1.3.0-7 Perl 5 modules for manipulating pd
ii libxml-writer-perl 0.604-1 Perl module for writing XML docume
ii perl 5.10.0-17 Larry Wall's Practical Extraction
ii python 2.5.2-3 An interactive high-level object-o
ii vim 1:7.1.314-3+lenny2 Vi IMproved - enhanced vi editor
vim-vimoutliner recommends no packages.
vim-vimoutliner suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
