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


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Chong Yidong <cyd <at> gnu.org>
Cc: lekktu <at> gmail.com, 11102 <at> debbugs.gnu.org
Subject: bug#11102: 24.0.94; C-x C-c from a client frame sometimes kills the whole Emacs process
Date: Sat, 14 Apr 2012 14:37:59 +0300
> From: Chong Yidong <cyd <at> gnu.org>
> Cc: lekktu <at> gmail.com,  11102 <at> debbugs.gnu.org
> Date: Sat, 14 Apr 2012 18:33:39 +0800
> 
> 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?

> That is the intended behavior, which is also the behavior on
> GNU/Linux when there is a graphical display available.  I think the
> patch I posted earlier should DTRT for Windows, if you or Juanma can
> try it.

Why does it make sense to have "-c -n" behave differently from "-t -n"?
Isn't this terribly confusing for users?  AFAIU, these two are variants
are otherwise very similar to each other: they both reuse the current
frame on the same terminal where the server is running.




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

Previous Next


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