From owner-freebsd-ports Tue Aug 19 05:37:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA02477 for ports-outgoing; Tue, 19 Aug 1997 05:37:54 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA02471 for ; Tue, 19 Aug 1997 05:37:49 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com (cssmuc.frt.dec.com [16.186.96.161]) by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) with SMTP id IAA01001; Tue, 19 Aug 1997 08:20:44 -0400 (EDT) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA00079; Tue, 19 Aug 1997 14:20:34 +0200 Message-Id: <9708191220.AA00079@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: Michael Elbel Cc: ports@freebsd.org, garyj@muc.de In-Reply-To: Message from Michael Elbel of Tue, 19 Aug 97 13:11:38 +0200. Reply-To: gjennejohn@frt.dec.com Subject: Re: XEmacs-19.15 port is bad Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Aug 97 14:20:34 +0200 X-Mts: smtp Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk me@muc.ditec.de writes: > Just use the 19.14 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:5 -4: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--- > well, the patch certainly works. I just tried it out. Way to go, Michael. > 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'd be voting against simply upgrading xemacs to 20.2. For one they're saying > it is still not yet considered an official upgrade path from 19.15. Then > the package is *still* larger than 19.15 and I'd frankly hesitate to use > it unless I'd need the MULE support. > > I'm suggesting: > a) additional patch to 19.15 so that it works again for everybody > b) if I get around to it or some other kind soul adapts the 19.15 port, > produce a new xemacs-20 port that contains 20.2 for all those that want > the new capabilities and are willing to live with what they'll pay for it -. > If I'm reading the README right, MULE is right in 20.2, so there'd be > no need for a separate port. > > Whaddaya say? I think the patch should definitely go into the 19.15 port. I'd suggest waiting on 20.X until it's officially released. Just MHO. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) garyj@muc.de (play) gj@freebsd.org