On Mon, 26 Dec 2005, Ciaran McCreesh wrote:
On Mon, 26 Dec 2005 12:02:37 -0500 (EST) Thomas Dickey <[EMAIL PROTECTED]>
wrote:
| I'm certain we're talking about something different, since neither
| vim nor screen uses any other interface in that area than termcap.
|
| I was just in screen yesterday, and am looking at vim right now, just
| in case some feature has crept in. If it were in fact using terminfo
| rather than termcap, it would call one of these functions:
<snip>
| All three of those programs use the same interface from ncurses - the
| termcap one.
Vim has --with-tlib=. If it's set to ncurses, everything works nicely.
If it's set to termcap it ends up mangling the screen.
The default value is ncurses though, as I read src/configure.in
case "`uname -s 2>/dev/null`" in
OSF1) tlibs="ncurses curses termlib termcap";;
*) tlibs="ncurses termlib termcap curses";;
esac
And there're two factors to consider: the terminal database, and the
library. Either may be a problem. But I don't offhand know of a problem
with either that would mangle the screen with GNU termcap. From the
termcap interface up, vim would do the same thing anyway since it's
a termcap application (uses tgetent, tgoto, etc). term.c is about 5400
lines of code...
Note that vim uses tgoto() rather than tparm() - and uses that for
updating colors. Not exactly the intended use of that function, but
it works.
| You might also consider --with-loadable-filters (that makes a smaller
| executable).
Hrm, if I add --with-loadable-filters to the 9.5 ebuilds I get a
compile error:
...
Looks like it's parallel build related. With MAKEOPTS=-j1 it goes away,
but with anything higher it fails consistently.
yes - I haven't done anything regarding parallel build for vile.
Only ncurses, iirc. I'll add that to my to-do list.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
gentoo-user@gentoo.org mailing list
