Re: [gentoo-user] vi & arrow keys
[EMAIL PROTECTED] said: > strange. Where did you get the vi from? > I thought the "vi" is a commercial product and not freely > available... /usr/portage/app-editors/vi >emerge unmerge vi >emerge vim did the trick. vim includes a /usr/bin/vi -> vim symlink. How would emerge react if I hadn't unmerged vi first? /A -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] vi & arrow keys
It turned out I was indeed using vi (and not vim, as I was in the RH box). emerging vim now, and we'll see what happens... Thanks for the pointer... /A -- [EMAIL PROTECTED] mailing list
[gentoo-user] vi & arrow keys
Hi, Anyone knows how to get the arrow keys to work in vi? If I'm in 'insert-mode' and I press '<-' I get a screen refresh and I get back to command mode so I have to press 'i' to get back to insert mode. The arrow keys do the right thing in command mode, though. My old RH box allows the arrows keys to be used in insert mode, so iknow it can be done /A -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Minimal Gentoo install
[EMAIL PROTECTED] said: > * Anders Eriksson (2003-07-26 10:16 +0200) > I'd like to add a warning here. I (being a longtime Linux and distcc > > user, albeit a gentoo newcommer) tried emerge -e world with distcc. > It turned out that zlib did NOT like that. For some reason it, > during > ./configure, decided that my system was not shared-object capable, > and skipped building the .so files. Not fun at all. Even distcc with > > just "127.0.0.1" in the group trigged it. > Is "localhost" the first entry in your DISTCC_HOSTS? According to > the man page: 'The literal word "localhost" is interpreted specially > to cause compilations to be directly executed, rather than passed to > a daemon on the local machine.' > Thorsten I tried both "localhost" "127.0.0.1" and "hostname.domain". No dice. I'll dig into it tomorrow (after openoffice compile...) /A -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Minimal Gentoo install
Hi folks, I'd like to add a warning here. I (being a longtime Linux and distcc user, albeit a gentoo newcommer) tried emerge -e world with distcc. It turned out that zlib did NOT like that. For some reason it, during ./configure, decided that my system was not shared-object capable, and skipped building the .so files. Not fun at all. Even distcc with just "127.0.0.1" in the group trigged it. I'm currently finishing -e world without distcc, I can provide details later if needed. /Anders -- [EMAIL PROTECTED] mailing list