GNU bug report logs - #55599
save-buffers-kill-emacs doesn't give a visible prompt when called from command line

Previous Next

Package: emacs;

Reported by: Peter Ludemann <peter.ludemann <at> gmail.com>

Date: Mon, 23 May 2022 19:57:02 UTC

Severity: normal

Tags: wontfix

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Peter Ludemann <peter.ludemann <at> gmail.com>
Cc: michael.albinus <at> gmx.de, 55599 <at> debbugs.gnu.org
Subject: Re: bug#55599: save-buffers-kill-emacs doesn't give a visible prompt
 when called from command line
Date: Wed, 01 Jun 2022 05:30:39 +0300
> From: Peter Ludemann <peter.ludemann <at> gmail.com>
> Date: Tue, 31 May 2022 12:34:23 -0700
> Cc: Michael Albinus <michael.albinus <at> gmx.de>, 55599 <at> debbugs.gnu.org
> 
> There's probably a solution to this, but it could be a lot of work for a small benefit.

Could you please describe the problem for which you are looking for a
solution?  During this discussion, you presented several issues that
bothered you, so I'm no longer sure which of those we are now talking
about.

> However, I noticed that stderr appears to be available, when there's an error:
> 
> $ emacsclient --eval '(man fprintf)'
> *ERROR*: Symbol’s value as variable is void: fprintf
> 
> and also when it works properly:
> 
> $ emacsclient --eval "(list-buffers)"
> #<window 194 on *Buffer List*>

That's emacsclient's stderr, not that of the daemon.  And it can only
print messages, not receive input.




This bug report was last modified 1 year and 311 days ago.

Previous Next


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