From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: read-event in batch mode
Date: Fri, 31 Jan 2014 17:03:21 +0200 [thread overview]
Message-ID: <83sis45h3a.fsf@gnu.org> (raw)
In-Reply-To: <jwvy51w1c16.fsf-monnier+emacs@gnu.org>
> 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.
As for others, I hope their users will speak up. If nothing else
turns up, I suggest to ifdef away this code after the release branch
is cut, and see if someone hollers.
> The "|| (IS_DAEMON && daemon_pipe[1] >= 0" part looks to me like "let's
> make sure the daemon mode works like --batch until we fork&detach".
> IOW if it's not needed for --batch, then it's not needed for the daemon
> case either.
That was my guess as well.
Thanks.
next prev parent reply other threads:[~2014-01-31 15:03 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 [this message]
2014-02-02 12:11 ` Nix
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=83sis45h3a.fsf@gnu.org \
--to=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).