Date: Wed, 08 Oct 1997 13:45:00 +0930 From: Mike Smith <mike@smith.net.au> To: itojun@itojun.org Cc: S ren Schmidt <sos@sos.freebsd.dk>, jkh@FreeBSD.ORG (Jordan K. Hubbard), current@FreeBSD.ORG Subject: Re: Status of perl and tcl in vi? Message-ID: <199710080415.NAA00674@word.smith.net.au> In-Reply-To: Your message of "Wed, 08 Oct 1997 06:55:38 %2B0900." <28450.876261338@coconut.itojun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> I guess in all the fracas over Tcl, we lost vi's tcl and perl > >> interpreters by default? I'm just now noticing that I can't do :tcl <blah> > >> anymore where it used to work, and given that I don't use this feature > >> very often I can also imagine that it might have left us some time ago > >> without my noticing. Weren't we going to allow vi to link with TCL > >> in -current unless NOTCL was set? > >> If we could get perl upgraded to perl5 in the tree, we could include > >> it too, heck. Bloat that vi binary! ;-) > >AAAARRRGGGGHHHHHHHH!!!!!!!!! > > I believe we'd better have very plain configuration (yes, no perl, > no tcl) in /usr/bin/vi , and have ports directory for vi + tcl/perl. > editors/nvi should be a good starting point. vi should be smart enough to dlopen() the relevant shared libraries and selectively enable/disable :tcl/:perl to suit the situation. mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710080415.NAA00674>