From: Eli Zaretskii <eliz@gnu.org>
To: Ioannis Kappas <ioannis.kappas@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>
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: Thu, 11 Feb 2021 16:09:28 +0200 [thread overview]
Message-ID: <831rdmitlz.fsf@gnu.org> (raw)
In-Reply-To: <CAMRHuGBP=UqDiBBJ18BWASmFwLTgx3WkQ50CrQK6B2t6K2mUbw@mail.gmail.com> (message from Ioannis Kappas on Thu, 11 Feb 2021 08:10:34 +0000)
> From: Ioannis Kappas <ioannis.kappas@gmail.com>
> Date: Thu, 11 Feb 2021 08:10:34 +0000
> Cc: 46388@debbugs.gnu.org
>
> > My reading of the code is that we already fflush stderr after emitting
> > a message, so this should already happen. See message_to_stderr. If
> > that still doesn't help, then there's some buffering in the OS (for
> > example, in the pipe machinery itself), which we cannot control.
>
> the xdisp.c:message_to_stderr() is the first function i studied with
> gdb when I started the investigation. Unless I've missed something,
> it does not seem to lead to calling fflush (under windows at least):
Then maybe this:
> /* Return the error output stream. */
> static FILE *
> errstream (void)
> {
> FILE *err = buferr;
> if (!err)
> return stderr;
> fflush_unlocked (stderr); <<<<<<<<<<<<<<<<
> return err;
> }
should be fixed to fflush 'buferr' instead (or in addition to stderr)?
Paul, isn't that a bug that we fflush stderr here, and not 'buferr'?
next prev parent reply other threads:[~2021-02-11 14:09 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
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 [this message]
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=831rdmitlz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46388@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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).