From owner-freebsd-ports Sun Aug 17 02:47:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19709 for ports-outgoing; Sun, 17 Aug 1997 02:47:24 -0700 (PDT) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19699 for ; Sun, 17 Aug 1997 02:47:19 -0700 (PDT) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.6/8.6.9) with ESMTP id LAA00484 for ; Sun, 17 Aug 1997 11:45:13 GMT Message-Id: <199708171145.LAA00484@peedub.muc.de> X-Mailer: exmh version 2.0delta 6/3/97 To: freebsd-ports@freebsd.org Subject: Re: XEmacs-19.15 port is bad Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 16 Aug 1997 18:49:13 MST." <199708170149.SAA17006@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Aug 1997 11:45:12 +0000 From: Gary Jennejohn Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gary Kline writes: > > > >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 > Interesting is that viper mode works just fine with xemacs-19.15p7 when invoked as "xemacs -nw". Go figure. I tried versions of xemacs with and without MOTIF (actually lesstif). Both fail when xemacs is invoked as an X app. It would probably be best to bring this to the attention of the xemacs developers. See comp.emacs.xemacs. I don't think the port maintainer is in a position to fix this himself. However, you might want to send-pr the suggestion to update the port to 20.X, although 20.X isn't officially released AFAIK. --- Gary Jennejohn Home - garyj@muc.de Work - gjennejohn@frt.dec.com