From owner-freebsd-current  Tue Oct  7 09:26:11 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA07831
          for current-outgoing; Tue, 7 Oct 1997 09:26:11 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07804;
          Tue, 7 Oct 1997 09:25:53 -0700 (PDT)
          (envelope-from sos@sos.freebsd.dk)
Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id SAA03958; Tue, 7 Oct 1997 18:25:05 +0200 (MEST)
From: Søren Schmidt <sos@sos.freebsd.dk>
Message-Id: <199710071625.SAA03958@sos.freebsd.dk>
Subject: Re: Status of perl and tcl in vi?
In-Reply-To: <199710071253.FAA06161@freefall.freebsd.org> from "Jordan K. Hubbard" at "Oct 7, 97 05:53:35 am"
To: jkh@FreeBSD.ORG (Jordan K. Hubbard)
Date: Tue, 7 Oct 1997 18:25:05 +0200 (MEST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Jordan K. Hubbard who wrote:
> 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!!!!!!!!!

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..