From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: lekktu@gmail.com, 11102@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 16:34:32 +0300 [thread overview]
Message-ID: <83iph21lp3.fsf@gnu.org> (raw)
In-Reply-To: <87zkaebgek.fsf@gnu.org>
> From: Chong Yidong <cyd@gnu.org>
> Cc: lekktu@gmail.com, 11102@debbugs.gnu.org
> Date: Sat, 14 Apr 2012 21:18:43 +0800
>
> Eli Zaretskii <eliz@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.
I'm relieved ;-)
> > 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.
Maybe it's just me, but the "aberration" sounds good to me, and,
again, makes "-c -n" and "-t -n" behave very similar, except for the
effect of "C-x C-c". I would suggest to make them similar in that
respect as well, so as to cause a bit less mental disorder to users
than we do now.
If we do leave the different "C-x C-c" behavior, we need to clearly
document that in the manual, I think.
next prev parent reply other threads:[~2012-04-14 13:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 18:56 bug#11102: 24.0.94; C-x C-c from a client frame sometimes kills the whole Emacs process Dani Moncayo
2012-03-30 17:01 ` Chong Yidong
2012-03-30 17:45 ` Eli Zaretskii
2012-03-30 20:29 ` Juanma Barranquero
2012-04-12 18:11 ` Juanma Barranquero
2012-04-13 14:38 ` Eli Zaretskii
2012-04-13 15:20 ` Dani Moncayo
2012-04-13 15:46 ` Eli Zaretskii
2012-04-13 23:49 ` Juanma Barranquero
2012-04-14 4:03 ` Chong Yidong
2012-04-14 7:26 ` Eli Zaretskii
2012-04-13 16:10 ` Juanma Barranquero
2012-04-13 16:13 ` Juanma Barranquero
2012-04-13 17:55 ` Eli Zaretskii
2012-04-13 19:15 ` Juanma Barranquero
2012-04-13 21:00 ` Eli Zaretskii
2012-04-14 4:55 ` Chong Yidong
2012-04-14 5:34 ` Chong Yidong
2012-04-14 7:25 ` Eli Zaretskii
2012-04-14 8:17 ` Chong Yidong
2012-04-14 9:28 ` Eli Zaretskii
2012-04-14 10:33 ` Chong Yidong
2012-04-14 11:37 ` Eli Zaretskii
2012-04-14 13:18 ` Chong Yidong
2012-04-14 13:34 ` Eli Zaretskii [this message]
2012-04-15 8:53 ` Chong Yidong
2012-04-20 8:23 ` Dani Moncayo
2012-04-20 19:10 ` Dani Moncayo
2012-04-14 9:36 ` Eli Zaretskii
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=83iph21lp3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11102@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=lekktu@gmail.com \
/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.