From owner-freebsd-ports Tue Aug 19 08:48:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA14053 for ports-outgoing; Tue, 19 Aug 1997 08:48:24 -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 IAA14044; Tue, 19 Aug 1997 08:48:20 -0700 (PDT) Received: (from uucp@localhost) by tera.com (8.7.5/8.7.3) with UUCP id IAA00394; Tue, 19 Aug 1997 08:47:29 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.5/8.7.3) id IAA23199; Tue, 19 Aug 1997 08:42:28 -0700 (PDT) From: Gary Kline Message-Id: <199708191542.IAA23199@tao.thought.org> Subject: Re: XEmacs-19.15 port is bad In-Reply-To: from Michael Elbel at "Aug 19, 97 02:29:00 pm" To: me@gw.muc.ditec.de Date: Tue, 19 Aug 1997 08:42:27 -0700 (PDT) Cc: kline@thought.org, ports@FreeBSD.ORG, asami@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Michael Elbel: > [[ ... ]] > Just use the old lisp/x11/x-win-xfree86.el and put it in your load-path > before anything else or apply the following patch: > > <<<<<<---snip--- > --- /usr/local/lib/xemacs-19.15/lisp/x11/x-win-xfree86.el Wed Dec 18 04:54:22 1996 > +++ x-win-xfree86.el Fri May 23 14:13:59 1997 > @@ -55,6 +55,6 @@ > (while mods > (let ((k1 (vector (append (car mods) foo))) > (k2 (vector (append (car mods) bar)))) > - (define-key key-translation-map k1 k2)) > + (define-key global-map k1 k2)) > (setq mods (cdr mods)))) > (setq mapping (cdr mapping))))) > <<<<<<---snip--- > > > Michael, if you're reading this list, now you know > > all that I have. > > Thanks. Now I'd like some advice - should we put this "fix" in the port? > It doesn't seem to disturb anything else, the file certainly only > gets loaded if you run XFree86. I think we're all pretty much in agreement re xemacs-19.15. Apply this patch to fix the ESC bug. Then do a separate port for xemacs-20.2. V19.15 would be the `stable' version, and 20.2 would be the cutting edge version with MULE. I have the feeling that the multi-language version of xemacs will be the one-true-XEmacs in the months ahead and that 19.15 will be consigned to history. > gary -- Gary D. Kline kline@tao.thought.org Public service uNix