From xemacs-m  Thu Jun 12 21:16:21 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id VAA24457
	for <xemacs-beta@xemacs.org>; Thu, 12 Jun 1997 21:16:19 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQctrs02471; Thu, 12 Jun 1997 22:05:59 -0400 (EDT)
Date: Thu, 12 Jun 1997 22:05:59 -0400 (EDT)
Message-Id: <QQctrs02471.199706130205@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Moscow success on Linux
In-Reply-To: <wuk9jzmp25.fsf@spline.la.asu.edu>
References: <wuk9jzmp25.fsf@spline.la.asu.edu>
X-Mailer: VM 6.33 under 20.3 "Moscow" XEmacs Lucid (beta6)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

John Jones writes:
 >  o I am seeing a minor bug (which were probably there before).  First,
 >    if I start XEmacs from an xterm, and then use gnuclient -nw, it
 >    works OK.  If I start XEmacs through my window manager and try
 >    gnuclient -nw, XEmacs crashes.  Looking at the entry for XEmacs
 >    with ps (before the crash :) ) shows a TTY of "1" for programs
 >    started through the Window manager.  This must be confusing the
 >    gnuclient -nw interaction.  (gnuclient without -nw for openning a
 >    new X frame works in all cases).

Crashes are major bugs.  Please send a stacktrace from the core
dump.  Even better would be the simplest recipe to reproduce the
crash that you can come up with.  gnuclient -nw attaches to an
XEmacs started from my window manager without incident, so there's
likely something unique going on in your environment.

