unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: annoying behavior of emacs --daemon
Date: Mon, 3 Nov 2008 22:34:16 -0800 (PST)	[thread overview]
Message-ID: <200811040634.mA46YGHE015780@mothra.ics.uci.edu> (raw)
In-Reply-To: <buood0wf3d0.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Tue, 04 Nov 2008 14:48:43 +0900")

Miles Bader <miles.bader@necel.com> writes:

  > When using --daemon, you initially have no frames.  You can then make
  > new frames with emacsclient -c or emacsclient -t, but if they're X
  > frames, closing the last such created frame (with C-x # or C-x C-c)
  > kills the emacs process!
  > 
  > This _doesn't_ happen if you use emacsclient -t, because it specifically
  > overrides those commands to do something reasonable.
  > 
  > It seems like all emacsclient -c created frames should use some similar
  > magic to what emacsclient -t uses, to prevent this annoying behavior.

I can't reproduce this...

Can you reproduce this with 
emacs -Q --daemon
?




  reply	other threads:[~2008-11-04  6:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04  5:48 annoying behavior of emacs --daemon Miles Bader
2008-11-04  6:34 ` Dan Nicolaescu [this message]
2008-11-04  7:28   ` Miles Bader
2008-11-04  8:55     ` Dan Nicolaescu
2008-11-04  9:47       ` Miles Bader
2008-11-04 13:03         ` Liang Wang
2008-11-04 13:49           ` Miles Bader
2008-11-04 16:48             ` Chong Yidong
2008-11-04 15:12         ` Dan Nicolaescu
2008-11-04 15:51           ` Miles Bader
2008-11-04  9:24     ` unclear [was: annoying] " Stephen J. Turnbull
2008-11-04 16:55       ` unclear Chong Yidong
2008-11-05 17:57         ` unclear Ulrich Mueller

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811040634.mA46YGHE015780@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).