From xemacs-m  Sat Feb  8 22:35:43 1997
Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id WAA19046
	for <xemacs-beta@xemacs.org>; Sat, 8 Feb 1997 22:35:42 -0600 (CST)
Received: from branagh.ta52.lanl.gov (branagh.ta52.lanl.gov [128.165.144.9]) by mailhost.lanl.gov (8.8.5/8.8.3) with SMTP id VAA26908 for <xemacs-beta@xemacs.org>; Sat, 8 Feb 1997 21:35:42 -0700 (MST)
Received: by branagh.ta52.lanl.gov (SMI-8.6/SMI-SVR4)
	id VAA01218; Sat, 8 Feb 1997 21:32:10 -0700
Date: Sat, 8 Feb 1997 21:32:10 -0700
Message-Id: <199702090432.VAA01218@branagh.ta52.lanl.gov>
From: "John A. Turner" <turner@branagh.ta52.lanl.gov>
To: xemacs-beta@xemacs.org
Subject: xemacs -nw
Reply-To: turner@lanl.gov

I have what's probably a dumb question.

Here's the situation.  This is under Solaris 2.5.1.  Say I'm in a tty
(xterm, dtterm, whatever), either telnetted to another machine or on
the console of my own machine but su'd to another user (or root or
whatever).  For whatever reason, my DISPLAY env. var. is set, and I
fire up xemacs -nw.  How come I get a bunch of:

Xlib: connection to "machine.blah.blah:0.0" refused by server
Xlib: Client is not authorized to connect to Server

messages?  Not just one, but a bunch (15?).  Then it finally starts up
and seems fine.

Why is it even messing with X?  Shouldn't it just ignore DISPLAY and
start in the tty.  Or does this not happen to others, or on other
platforms?

I poked around the FAQ and even (hope you're sitting) the manual, but
didn't see anything about this.  The descrip. of -nw just says:

`-nw'
     Start up XEmacs in TTY mode (using the TTY XEmacs was started
     from), rather than trying to connect to an X display.  Note that
     this happens automatically if the `DISPLAY' environment variable
     is not set.

So is this a bug, or have I just found another new and wondrous way to
be an idiot?  Hmm, I just tried 19.14 on several machines other than
my own:

Solaris 2.5.1 => same behavior
AIX => no problem
DUNIX 3.2 => no problem

Also tried not-XEmacs 19.34 on DUNIX 3.2 => no problem

What's going on?

-- 
John Turner
http://www.lanl.gov/home/turner

