peter 2bfd97fd32 When using the perl5 extensions, ask perl itself what the pathnames are, ... don't just hard code them into the Makefile. (This is the optional stuff to use perl scripts as a vi scripting language. eg, to load a sample script, type: :perl do 'wc.pl'; this loads /usr/share/vi/perl/wc.pl to add the "wc" command. Then, one can do this: :perl wc Yes, this is a trivial example. There are more useful examples, eg 'make' output parsing along the lines of emacs's "compile" mode. The tcl extension is similar and enabled by default since we ship with tcl.)		1996-12-30 09:24:19 +00:00
..
config.h	The tcl/perl interpreter compile options were not really optional.	1996-11-03 19:15:45 +00:00
Makefile	When using the perl5 extensions, ask perl itself what the pathnames are,	1996-12-30 09:24:19 +00:00
pathnames.h	Fix PATH_MSGCAT	1996-11-04 02:28:31 +00:00
port.h	Update to use nvi-1.79 sources	1996-11-01 08:16:24 +00:00