From: Eli Zaretskii <eliz@gnu.org>
To: Peter Ludemann <peter.ludemann@gmail.com>
Cc: michael.albinus@gmx.de, 55599@debbugs.gnu.org
Subject: bug#55599: save-buffers-kill-emacs doesn't give a visible prompt when called from command line
Date: Sat, 28 May 2022 22:25:53 +0300 [thread overview]
Message-ID: <83fsktlari.fsf@gnu.org> (raw)
In-Reply-To: <CAHjfyZ0ozXXENWVY2p18MCA1xtVWg3QizzaQBD+eDB+076oN9g@mail.gmail.com> (message from Peter Ludemann on Sat, 28 May 2022 11:27:22 -0700)
> From: Peter Ludemann <peter.ludemann@gmail.com>
> Date: Sat, 28 May 2022 11:27:22 -0700
> Cc: Michael Albinus <michael.albinus@gmx.de>, 55599@debbugs.gnu.org
>
> It seems that there is a way to get an interactive message to the terminal in batch mode ...
>
> During daemon startup (with an existing .emacs.desktop file), I get this on my terminal:
>
> bunzip2ing contrib-protobufs-2021-06-07-15-56.tbz2...
> bunzip2ing contrib-protobufs-2021-06-07-15-56.tbz2...done
> Parsing tar file...
> Parsing tar file...done
> Please type y, n, ! or i, or C-v/M-v to scroll:
>
> This seems to be from make-progress-reporter, which (if I read the code correctly) ends up calling
> (message "%s %s %s" text pulse-char suffix)). And that message displays interactively on the terminal.
During startup of the daemon, it can still have its original standard
output/error streams (and even that is not guaranteed if it is not
invoked from the shell prompt), but once it starts, the standard
output/error streams are closed b y the system and are no longer
available, AFAIK.
> So, there is a way to have the messages from emacsclient --eval display on the terminal, but in some
> (most?) situations they don't. (The definition for message says: "In batch mode, the message is printed to
> the standard error stream, followed by a newline.") So, I infer that yes-or-no-p should just use "message"
> and all will be fine.
yes-or-no-p needs to ask a question and get the response.
> As to your suggested feature request: I'm not requesting termination of the server non-interactively - I'm just
> saying that when the shutdown command comes from the command line, the messages be output to the
> terminal, the way "message" does and not the way yes-or-no-p does.
The terminal is still taken by the client frame it displays.
next prev parent reply other threads:[~2022-05-28 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 19:56 bug#55599: save-buffers-kill-emacs doesn't give a visible prompt when called from command line Peter Ludemann
2022-05-24 7:34 ` Michael Albinus
2022-05-24 9:29 ` Peter Ludemann
2022-05-24 11:31 ` Eli Zaretskii
2022-05-28 18:27 ` Peter Ludemann
2022-05-28 19:25 ` Eli Zaretskii [this message]
2022-05-28 19:39 ` Eli Zaretskii
2022-05-31 19:34 ` Peter Ludemann
2022-06-01 2:30 ` Eli Zaretskii
2022-06-01 17:54 ` Peter Ludemann
2022-06-01 19:52 ` Eli Zaretskii
2022-06-01 20:04 ` Peter Ludemann
2023-09-13 1:43 ` Stefan Kangas
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=83fsktlari.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55599@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=peter.ludemann@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).