GNU bug report logs - #11102
24.0.94; C-x C-c from a client frame sometimes kills the whole Emacs process

Previous Next

Package: emacs;

Reported by: Dani Moncayo <dmoncayo <at> gmail.com>

Date: Tue, 27 Mar 2012 19:29:01 UTC

Severity: normal

Found in version 24.0.94

Done: Chong Yidong <cyd <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Chong Yidong <cyd <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: lekktu <at> gmail.com, 11102 <at> debbugs.gnu.org
Subject: Re: bug#11102: 24.0.94;
	C-x C-c from a client frame sometimes kills the whole Emacs process
Date: Sat, 14 Apr 2012 21:18:43 +0800
Eli Zaretskii <eliz <at> gnu.org> writes:

>> The issue which Dani and Juanma were talking about is a separate one:
>> for a graphical Emacs on Windows, "emacsclient -c -n foo.txt" ought to
>> create a new frame with a `client' parameter, so that C-x C-c exits
>> Emacs instead of closing just that frame.
>
> Now I'm completely confused: didn't you say that "C-x C-c" should
> _not_ exit Emacs in this case?

Sorry, I miswrote.  Indeed, C-x C-c should _not_ exit Emacs in that
case.

> Why does it make sense to have "-c -n" behave differently from
> "-t -n"?

The "-t -n" case is an abberation; emacsclient could even signal an
error for that, because it is saying "open on this text terminal, but
don't wait", which is nonsensical.  The current behavior, of opening on
another text terminal, is a fudge---and one that doesn't work for the
Emacs daemon.  For that reason, the discrepancy you point out is not
important.




This bug report was last modified 13 years and 34 days ago.

Previous Next


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