Date: Sat, 25 Jan 2003 19:22:15 -0800 From: Paul Hoffman <phoffman@proper.com> To: questions@FreeBSD.ORG Subject: Re: A vi for /bin? Message-ID: <p05210200ba59031c28c6@[165.227.249.18]> In-Reply-To: <20030126023004.GG18454@dan.emsphone.com> References: <KOEDJPGCNAIOODFOCJJIEEAIGDAA.petersen@fully.qualified.domain.name> <p05210202ba58f08ccec6@[165.227.249.18]> <20030126023004.GG18454@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:36 AM +0000 1/26/03, Petersen wrote:
>Assuming you have the object files from a buildworld hanging around, then
>cd /usr/obj/usr/src/usr.bin/vi
>cc -O -pipe -o vi *.o -lncurses -static && strip vi && mv vi /bin/
>should probably supply you with what you want.
Two modifications made this work fine:
- I hadn't done a buildworld, but doing the following got the same result:
cd /usr/src/usr.bin/vi
make && cc -O -pipe -o vi *.o -lncurses -static && strip vi && mv vi /bin/
- As pointed out off-line, you also need to get it the termcap library. Doing
cp /usr/share/misc/termcap.db /root/.termcap.db
fixes that.
At 8:30 PM -0600 1/25/03, Dan Nelson wrote:
>You
>might want to install e3, which is only 13k statically linked and uses
>generic ANSI escape codes so it doesn't need a termcap file. If run as
>e3vi, it acceptes vi keystrokes.
Nice! e3 built from the ports collection linked statically
automatically. e3 didn't work correctly on my console (it didn't
recognize the Alt key), but e3vi worked fine and felt just like vi.
Thanks! I now feel better about emergencies.
--Paul Hoffman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05210200ba59031c28c6>