GNU bug report logs - #46388
27.1; emacs -batch does not output messages immediately when invoked outside of the command prompt

Previous Next

Package: emacs;

Reported by: Ioannis Kappas <ioannis.kappas <at> gmail.com>

Date: Mon, 8 Feb 2021 21:22:02 UTC

Severity: normal

Found in version 27.1

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


Message #50 received at 46388 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ioannis Kappas <ioannis.kappas <at> gmail.com>
Cc: 46388 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu
Subject: Re: bug#46388: 27.1; emacs -batch does not output messages
 immediately when invoked outside of the command prompt
Date: Fri, 12 Feb 2021 22:03:40 +0200
> From: Ioannis Kappas <ioannis.kappas <at> gmail.com>
> Date: Fri, 12 Feb 2021 19:59:02 +0000
> Cc: Paul Eggert <eggert <at> cs.ucla.edu>, 46388 <at> debbugs.gnu.org
> 
> How do you suggest we flush the message out so that it is always
> displayed to the user irrespective of the architecture/prompt it is
> ran on? Is there perhaps an elisp function to flush messages out (e.g.
> (progn (message "...") (message-flush!) (sit-for ...))) ?
> 
> So far we said:
> 1. We don't want to a solution where the emacs -batch's stderrr is
> forced to unbuffered mode (original patch proposal)
> 2. message_to_stderr() does not directly or indirectly invoke stderr
> flush (at least in windows).

As I said, this cannot be helped, not until we teach Emacs on Windows
to use the pseudo-console.  This is how the platform behaves when we
use pipes.

Sorry, there's no way around this.




This bug report was last modified 4 years and 71 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.