From xemacs-m  Wed Apr  2 10:37:08 1997
Received: from lehman.Lehman.COM (lehman.Lehman.COM [192.147.66.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id KAA16861
	for <xemacs-beta@xemacs.org>; Wed, 2 Apr 1997 10:37:06 -0600 (CST)
Received: (from smap@localhost) by lehman.Lehman.COM (8.6.12/8.6.12) id LAA24819; Wed, 2 Apr 1997 11:37:00 -0500
Received: from relay.messaging-svcs2.lehman.com(146.127.39.20) by lehman via smap (V1.3)
	id tmp024814; Wed Apr  2 11:36:55 1997
Received: from cfdev1425.lehman.com by relay.lehman.com (4.1/LB-0.6)
	id AA11211; Wed, 2 Apr 97 11:36:53 EST
Received: from localhost by cfdev1425.lehman.com (4.1/Lehman Bros. V1.6)
	id AA13146; Wed, 2 Apr 97 11:36:52 EST
Message-Id: <9704021636.AA13146@cfdev1425.lehman.com>
Reply-To: Rick Campbell <rickc@lehman.com>
X-Windows: The first fully modular software disaster.
Organization: Lehman Brothers Inc.
From: Rick Campbell <rickc@lehman.com>
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Cc: Martin Buchholz <mrb@eng.sun.com>
Subject: Miscellaneous issues (Linux, Dired, & Sparcworks) with 19.15
X-Pgp-Version: 2.6.2
X-Pgp-Signed: iQCVAwUBM0KLGltTztlqB385AQFbgQP/bcw+ys9QJ+jwTDaqSrKFmYaDGr1XuJfG
	      C6snbX2WmG0CphNPByPfDyfnxzqNCAtc+rxo5rD/LwlCjnjUtry5eui21pzN5RiX
	      oCgWG+x06cI/l9KdYwCTfui7/RjtH7uI4VyNZDiH3hCFPYcpHsa6Br6EwVCk5Obr
	      FgQU3Ki1vSU=
	      =4p4r
Date: Wed, 02 Apr 1997 11:36:49 -0500
Sender: rickc@lehman.com

First and foremost, 19.15 looks great.  But of course there are a few
issues...

In no particular order:

 - What is the status on Linux binaries?  Can someone tell me how to
   extract the goods from an RPM on non-RedHat (Slackware 3.*)
   systems.  Will there be a good old .tar.gz file as there is for
   other platforms?  If an RPM is basically a .tar.gz with some
   additional header info, can I just strip off the extra stuff
   somehow?

   Should I be building this myself and dropping it in incoming on
   ftp.xemacs.org?

 - In dired mode, if you execute describe-mode (C-h m), the *Help* buffer
   includes ``For the full dired info tree, type C-u h'', however, if
   you execute dired-describe-mode with a prefix argument (C-u h), you
   get an error message ``Info file dired does not exist''.  Perusing
   $XEMACS/lib/xemacs-19.15/info/ suggests that the dired info is, in
   fact, missing.

   Should I even ask who's bright idea it was to have an easier
   binding for rmail than rename in dired mode?!?!  As I updated my
   init file, I noticed that I'd already special cased the `r' binding
   for when I'm running FSF's version.  Sigh.....
   
 - With a SunOS 4.1.3 Sparcworks binary, the -nw switch does not
   prevent xemacs from attempting to connect to an X server if DISPLAY
   is set.  To demonstrate, set DISPLAY to a server to which you are
   not permitted to connect and then run ``xemacs -nw''.  Presumeably
   this is related to trying to use the display as a path to a
   tooltalk server, however it's worth noting that it behaves the same
   way if you run this all inside a shell created with ``ttsession -c
   $SHELL''.  This bug also exists in 19.14.

   I'm guessing that this is related to the 19.14 bug that causes
   these binaries to go absolutely apeshit (requiring machine reboot)
   if the X server goes away before the xemacs process does, although
   (for obvious reasons), I haven't verified that this bug exists for
   19.15.  I also have not yet verified that these things occur with
   the Solaris Sparcworks binaries and that they don't with the
   non-Sparcworks binaries.  I'll probably get to these things
   tomorrow as I'm working from home today.

   Still, EOS support is so much better than dbx mode (like it
   actually locates the sources files!) that it's worth putting up
   with even serious problems like the above.

			Rick

