unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Peter Ludemann <peter.ludemann@gmail.com>
Cc: 55599@debbugs.gnu.org
Subject: bug#55599: save-buffers-kill-emacs doesn't give a visible prompt when called from command line
Date: Tue, 24 May 2022 09:34:57 +0200	[thread overview]
Message-ID: <87r14jo02m.fsf@gmx.de> (raw)
In-Reply-To: <CAHjfyZ1yaJHqvkBkkw7zRktZJVA6xC+j-aPehGVERrKmtPbQiw@mail.gmail.com> (Peter Ludemann's message of "Mon, 23 May 2022 12:56:17 -0700")

Peter Ludemann <peter.ludemann@gmail.com> writes:

Hi Peter,

> When I try to kill an emacs server from the command line by:
>    emacsclient -e '(save-buffers-kill-emacs)'
> nothing appears to happen if there are any unsaved buffers.
>
> I presume that this is because the prompt goes to the usual place (below
> the mode line in the screen), which of course isn't visible from the
> command line because there isn't any screen when using "emacsclient -e".
>
> This is a follow-up to bug 55560, where it was suggested that kill-emacs is
> inappropriate and instead I should use save-buffers-kill-emacs.

There is an optional ARG which lets Emacs silently save all file-visiting
buffers without asking. So you must call

  emacsclient -e '(save-buffers-kill-emacs t)'

Best regards, Michael.





  reply	other threads:[~2022-05-24  7:34 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 [this message]
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
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=87r14jo02m.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=55599@debbugs.gnu.org \
    --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).