From: Eli Zaretskii <eliz@gnu.org>
To: Ioannis Kappas <ioannis.kappas@gmail.com>
Cc: 46388@debbugs.gnu.org
Subject: bug#46388: 27.1; emacs -batch does not output messages immediately when invoked outside of the command prompt
Date: Tue, 09 Feb 2021 00:36:33 -0500 [thread overview]
Message-ID: <E1l9LhR-0002lF-EV@fencepost.gnu.org> (raw)
In-Reply-To: <CAMRHuGDC-XAznW-0YtpnCncFkxBRywx-jDgZ2eQf8UNdebR8Og@mail.gmail.com> (message from Ioannis Kappas on Mon, 8 Feb 2021 21:42:09 +0000)
> From: Ioannis Kappas <ioannis.kappas@gmail.com>
> Date: Mon, 8 Feb 2021 21:42:09 +0000
>
> A solution thus to correct this behavior in emacs -batch on
> windows-nt would be to check if it is connected to the console,
> and when not, set stderr mode to unbuffered.
Thanks for the analysis and the patch proposal. However, I don't
think this is a good idea. For starters, stderr could be connected to
a file, in which case we do want it to be buffered. More generally,
stderr could be used for something other than outputting urgent
messages, in which case making it unbuffered will make I/O less
efficient for no good reason. And this would make Emacs on Windows
behave differently from Posix systems, which is also a downside.
I think a much better way forward in this area is to teach Emacs to
use the Pseudo Consoles introduced in recent Windows versions. That
would allow us to support subprocess communications via PTYs on
MS-Windows, and thus will solve this and other similar issues.
Patches to support PTYs on Windows are welcome.
next prev parent reply other threads:[~2021-02-09 5:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 21:20 bug#46388: 27.1; emacs -batch does not output messages immediately when invoked outside of the command prompt Ioannis Kappas
2021-02-08 21:42 ` Ioannis Kappas
2021-02-09 5:36 ` Eli Zaretskii [this message]
2021-02-09 20:15 ` Ioannis Kappas
2021-02-09 20:52 ` Eli Zaretskii
2021-02-09 21:14 ` Eli Zaretskii
[not found] ` <CAMRHuGC_p59uw_hmCL65Z0F1ZdFbVAf9MHcB-sX88bW6jchC-Q@mail.gmail.com>
2021-02-10 12:48 ` Ioannis Kappas
2021-02-10 15:57 ` Eli Zaretskii
2021-02-11 8:10 ` Ioannis Kappas
2021-02-11 14:09 ` Eli Zaretskii
2021-02-11 19:25 ` Ioannis Kappas
2021-02-11 19:55 ` Eli Zaretskii
2021-02-12 19:59 ` Ioannis Kappas
2021-02-12 20:03 ` Eli Zaretskii
2021-03-06 15:00 ` Ioannis Kappas
2021-03-08 4:05 ` Paul Eggert
2021-03-08 7:56 ` Ioannis Kappas
2021-03-11 14:27 ` Eli Zaretskii
2021-03-11 18:43 ` Paul Eggert
2021-02-11 21:15 ` Paul Eggert
2021-02-09 3:38 ` 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
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=E1l9LhR-0002lF-EV@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=46388@debbugs.gnu.org \
--cc=ioannis.kappas@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 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).