From: Nix <nix@esperi.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: read-event in batch mode
Date: Sun, 02 Feb 2014 12:11:28 +0000 [thread overview]
Message-ID: <87iosx90jz.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <83sis45h3a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 Jan 2014 17:03:21 +0200")
On 31 Jan 2014, Eli Zaretskii said:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: emacs-devel@gnu.org
>> Date: Fri, 31 Jan 2014 09:09:14 -0500
>>
>> > Does any port for a supported platform need this fragment, or can we
>> > safely delete it? What about the daemon -- does it need this "when
>> > detaching from the terminal", and if so, why?
>>
>> I suspect this code was written so that "emacs --batch" can read input
>> from stdin. If the other code works for that, than we can presumably
>> get rid of this code.
>
> Well, the systems that support D-Bus certainly don't need it, as they
> haven't been using that code since last May. Windows doesn't need
> that, either.
That would be around the time when emacs --daemon started "acting up" by
going into an unresponsive CPU-chewing loop whenever it asked a question
on the console during startup. I have to start Emacs these days by
starting a non-daemon Emacs, answering various questions (mostly from
desktop.el), quitting (and saving a fixed desktop file), then restarting
in daemon mode...
--
NULL && (void)
next prev parent reply other threads:[~2014-02-02 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 11:48 read-event in batch mode Eli Zaretskii
2014-01-31 13:43 ` Michael Albinus
2014-01-31 14:58 ` Eli Zaretskii
2014-01-31 15:34 ` Stefan Monnier
2014-01-31 16:16 ` Eli Zaretskii
2014-02-04 11:54 ` Michael Albinus
2014-02-04 15:57 ` Eli Zaretskii
2014-02-04 18:16 ` Stefan Monnier
2014-01-31 14:09 ` Stefan Monnier
2014-01-31 15:03 ` Eli Zaretskii
2014-02-02 12:11 ` Nix [this message]
2014-02-02 15:59 ` Eli Zaretskii
2014-02-02 19:25 ` Michael Albinus
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=87iosx90jz.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).