From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17510@debbugs.gnu.org, dmantipov@yandex.ru
Subject: bug#17510: 24.3.91; Problem with `emacs --daemon' in cygw32 build
Date: Mon, 19 May 2014 15:25:40 -0400 [thread overview]
Message-ID: <537A5AB4.8070602@cornell.edu> (raw)
In-Reply-To: <837g5hd8cf.fsf@gnu.org>
On 5/19/2014 12:46 PM, Eli Zaretskii wrote:
> I guess it's OK for the branch, thanks. But it strikes me that simply
> replacing the car of dpyinfo->name_list_element by something like
> "!!!DELETED DISPLAY!!!", or even just an empty string, would serve the
> same purpose, and save us the nuisance of an additional list in
> cygw32_display_name_list. After all, all you need is to mark a
> display deleted without actually deleting it, right? IOW, the main
> problem is in x_delete_display, and all the rest is just the overhead
> you needed to fix that, correct?
I think that's correct, and I agree that there should be a much simpler
fix. I'll have to look into the code and try to understand better
exactly what happens when emacs is started as a daemon and then a client
frame is opened and closed.
I'll hold off on installing my patch until I see if I can find a better
solution that is still safe enough for the branch.
Ken
next prev parent reply other threads:[~2014-05-19 19:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 17:50 bug#17510: 24.3.91; Problem with `emacs --daemon' in cygw32 build Ken Brown
2014-05-16 20:06 ` Ken Brown
2014-05-17 23:39 ` Ken Brown
2014-05-18 4:32 ` Eli Zaretskii
2014-05-18 14:30 ` Ken Brown
2014-05-18 15:11 ` Eli Zaretskii
2014-05-18 19:36 ` Ken Brown
2014-05-19 12:03 ` Ken Brown
2014-05-19 16:46 ` Eli Zaretskii
2014-05-19 17:31 ` Eli Zaretskii
2014-05-19 19:25 ` Ken Brown [this message]
2014-05-24 12:38 ` Ken Brown
2014-05-24 12:59 ` Eli Zaretskii
2014-05-24 18:14 ` Ken Brown
2014-05-24 22:18 ` Ken Brown
2014-05-24 19:28 ` Daniel Colascione
2014-05-24 22:18 ` Ken Brown
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=537A5AB4.8070602@cornell.edu \
--to=kbrown@cornell.edu \
--cc=17510@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
/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.