From: "Sewall, Jason" <jason.sewall@intel.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 15037@debbugs.gnu.org
Subject: bug#15037: Display can't be opened (display newer than emacs session)
Date: Wed, 7 Aug 2013 17:37:34 +0000 [thread overview]
Message-ID: <C64EEADE742C444EA672808682DC050459B003D7@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <A56114DC-2944-4E8F-BF01-F9F680FDF85A@swipnet.se>
> From: Jan Djärv [mailto:jan.h.d@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
next prev parent reply other threads:[~2013-08-07 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 20:52 bug#15037: Display can't be opened (display newer than emacs session) Sewall, Jason
2013-08-07 0:03 ` Glenn Morris
2013-08-07 17:39 ` Sewall, Jason
2013-08-07 8:32 ` Jan Djärv
2013-08-07 17:37 ` Sewall, Jason [this message]
2013-08-07 14:30 ` Stefan Monnier
2013-08-07 17:31 ` Sewall, Jason
2013-08-07 18:19 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C64EEADE742C444EA672808682DC050459B003D7@ORSMSX104.amr.corp.intel.com \
--to=jason.sewall@intel.com \
--cc=15037@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.