GNU bug report logs - #15037
Display can't be opened (display newer than emacs session)

Previous Next

Package: emacs;

Reported by: "Sewall, Jason" <jason.sewall <at> intel.com>

Date: Tue, 6 Aug 2013 21:02:02 UTC

Severity: normal

Tags: notabug

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=651431

Full log

Message #23 received at 15037 <at> debbugs.gnu.org (full text, mbox):

From: "Sewall, Jason" <jason.sewall <at> intel.com>
To: Jan Djärv <jan.h.d <at> swipnet.se>
Cc: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>,
 "15037 <at> debbugs.gnu.org" <15037 <at> debbugs.gnu.org>
Subject: RE: bug#15037: Display can't be opened (display newer than emacs
 session)
Date: Wed, 7 Aug 2013 17:37:34 +0000

> From: Jan Djärv [mailto:jan.h.d <at> swipnet.se]
> Sent: Wednesday, August 7, 2013 1:33 AM

> That is not what Emacs does.  "Reading available displays" is not possible.
> Emacs just tries to connect when you do open display.

Makes sense. 

> Did you kill the old server and start a new server in the same shell as you
> started the first?  My guess is that you did not, and so the second server
> either gets the correct authentication and thus can connect.

If you mean kill emacs and restart it, I could certainly do that (it will work, from past experience) but it defeats the purpose from my point of view. I'd like emacs to be able to create a frame on any display I ask it to, no matter the relative age of the emacs session and the remote display. If you mean (server-start), that is easy to do, but my understanding is that it has nothing to do with remote displays. Indeed, if I do emacs -Q (i.e., starting no servers) I am able to do that make-frame-on-display without trouble (for an emacs newer than the display)

> To really see what is going on you would need to debug Emacs with gdb
> when the make-frame-on-display fails.

While that is fine, as a somewhat experienced programmer and noob with Emacs internals, I am very surprised there isn't a higher-level way to debug this sort of problem in emacs-lisp. It isn't something I have the time to figure up right now at any rate.

Cheers,
Jason
This bug report was last modified 11 years and 287 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.