From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org, Espen Wiborg <espenhw@grumblesmurf.org>
Subject: Re: y-or-n-p and emacs --daemon
Date: Thu, 04 Dec 2008 08:15:11 -0500 [thread overview]
Message-ID: <jwvk5agt7ed.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <18743.48104.822687.186192@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Thu, 4 Dec 2008 12:15:52 +0100")
>> Ideally, either the question comes before detaching and it should then
>> behave as it does in -batch,
> I think that this is unaccaptable. A daemon shouldn't be interactive
> before detaching. Besides, there might not be any terminal associated
> with stdin, so this doesn't solve the problem for this case.
My comment was not intended to imply that this will solve all problems.
But it will at least make the code work as close to its intended
behavior as possible.
Now it will indeed be the case that the daemon will often be started
non-interactively, in which case any form of interactivity is
undesirable. This is a separate problem. I'm not sure how best to
solve it, tho if we can detect that stdin=/dev/null (i.e. when we reach
EOF on stdin) we might want to signal an error, like you propose.
Stefan
prev parent reply other threads:[~2008-12-04 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 10:44 y-or-n-p and emacs --daemon Ulrich Mueller
2008-12-03 11:11 ` Espen Wiborg
2008-12-03 19:33 ` Chong Yidong
2008-12-03 19:53 ` Dan Nicolaescu
2008-12-03 21:07 ` Chong Yidong
2008-12-03 21:53 ` Dan Nicolaescu
2008-12-04 1:05 ` Stephen J. Turnbull
2008-12-04 2:16 ` Stefan Monnier
2008-12-04 3:02 ` Dan Nicolaescu
2008-12-04 5:29 ` Stefan Monnier
2008-12-04 11:15 ` Ulrich Mueller
2008-12-04 11:28 ` Thierry Volpiatto
2008-12-04 13:15 ` Stefan Monnier [this message]
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=jwvk5agt7ed.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=espenhw@grumblesmurf.org \
--cc=ulm@gentoo.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.