From owner-freebsd-current  Tue Oct  7 05:54:07 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id FAA23449
          for current-outgoing; Tue, 7 Oct 1997 05:54:07 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23441
          for <current@FreeBSD.org>; Tue, 7 Oct 1997 05:54:04 -0700 (PDT)
          (envelope-from jkh@FreeBSD.org)
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Received: (from jkh@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id FAA06161
	for current; Tue, 7 Oct 1997 05:53:35 -0700 (PDT)
Date: Tue, 7 Oct 1997 05:53:35 -0700 (PDT)
Message-Id: <199710071253.FAA06161@freefall.freebsd.org>
To: current@FreeBSD.ORG
Subject: Status of perl and tcl in vi?
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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! ;-)

					Jordan