From: Robert Horn <rjhorn@alum.mit.edu>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 17847@debbugs.gnu.org
Subject: bug#17847: 24.3; Emacsclient hang/crash
Date: Wed, 25 Jun 2014 15:15:04 -0400 [thread overview]
Message-ID: <m3bntg94xz.fsf@hp-toy.robs.office> (raw)
In-Reply-To: <8361jpq62y.fsf@gnu.org>
Eli Zaretskii writes:
>> From: Robert Horn <rjhorn@alum.mit.edu>
>> Date: Wed, 25 Jun 2014 11:32:19 -0400
>>
>> Minimal test:
>>
>> 1. Start emacs --daemon -Q -s test
>> 2. Start emacsclient --alternate-editor="" -c -s test
>> 3. Exit emacsclient with c-X 5 0
>> 4. Repeat 2. and 3. until fail (3-6 tries typically)
>>
>> Failure is a momentary appearance of the X-window frame for the
>> emacsclient. After it is gone, the emacs daemon has also exited.
>>
>> Related test:
>> 1. Start emacs --daemon -s test (full startup with configuration
>> indicated below).
>> 2., 3., 4. the same
>
> What's the significance of all the non-default options in this recipe?
> Does the problem only happen if you use precisely those options? If
> so, can you tell why you need them?
I retested the minimal with starting emacs using "emacs --daemon -Q"
and emacsclient using "emacsclient -c". The results are the same.
After 5 cycles there is the momentary appearence of the X-window frame,
then both emacs and emacsclient processes have exited.
They were in there as leftovers from my old setup where I want
emacsclient to go to a particular socket and start emacs automatically
if there is not a daemon running already.
R Horn
next prev parent reply other threads:[~2014-06-25 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 15:32 bug#17847: 24.3; Emacsclient hang/crash Robert Horn
2014-06-25 16:58 ` Eli Zaretskii
2014-06-25 19:15 ` Robert Horn [this message]
2021-07-14 9:43 ` Lars Ingebrigtsen
2021-07-14 14:28 ` Robert Horn
2021-07-14 14:30 ` Lars Ingebrigtsen
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=m3bntg94xz.fsf@hp-toy.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=17847@debbugs.gnu.org \
--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.