From owner-freebsd-ports Sat Aug 16 19:18:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24754 for ports-outgoing; Sat, 16 Aug 1997 19:18:17 -0700 (PDT) Received: from tera.com (tera.tera.com [207.108.223.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA24749 for ; Sat, 16 Aug 1997 19:18:14 -0700 (PDT) Received: (from uucp@localhost) by tera.com (8.7.5/8.7.3) with UUCP id TAA16853 for freebsd-ports@freebsd.org; Sat, 16 Aug 1997 19:17:29 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.5/8.7.3) id SAA17006; Sat, 16 Aug 1997 18:49:13 -0700 (PDT) Date: Sat, 16 Aug 1997 18:49:13 -0700 (PDT) Message-Id: <199708170149.SAA17006@tao.thought.org> From: Gary Kline MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-ports@freebsd.org Subject: XEmacs-19.15 port is bad X-Mailer: VM 6.31 under 20.2 XEmacs Lucid Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After some weeks of using the ports version of xemacs-19.15p7 and trying to get it to work in vi|viper-mode, I gave up and installed the v20.2 release. With identical _dot_ files, this version does work. So I've got my vi that I've been using forever, and the best of the emacs suite. I'd suggest that we up-rev to v20.X and perhaps let anyone else who has been head-banging that our port doesn't work completely. The cause might be that the viper code is not in the load-path, but this is merely a ballpark guess. I didn't dig into the code... A note of thanks to Gary Jennejohn on the Eastern side of the pond for confirming this and saving me from surrender! gary kline PS: If this should be a gnats-pr, would someone clue me in on the syntax so that I can issue a bug report? Like to save others from this hassle. -gdk