GNU bug report logs - #79560
[PATCH] Do not erase the output buffer upon empty command

Previous Next

Package: emacs;

Reported by: Manuel Giraud <manuel <at> ledu-giraud.fr>

Date: Fri, 3 Oct 2025 06:49:01 UTC

Severity: normal

Tags: patch

Done: Eli Zaretskii <eliz <at> gnu.org>

To reply to this bug, email your comments to 79560 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#79560; Package emacs. (Fri, 03 Oct 2025 06:49:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Manuel Giraud <manuel <at> ledu-giraud.fr>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Fri, 03 Oct 2025 06:49:02 GMT) Full text and rfc822 format available.

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

From: Manuel Giraud <manuel <at> ledu-giraud.fr>
To: bug-gnu-emacs <at> gnu.org
Subject: [PATCH] Do not erase the output buffer upon empty command
Date: Fri, 03 Oct 2025 08:47:29 +0200
[Message part 1 (text/plain, inline)]
Tags: patch

Hi,

This patch prevents running an asynchronous empty command.  Should the
user mistakenly enter "M-& <RET>", it won't create and pop up an empty
*Async Shell Command* buffer.  It also has the nice property of not
erasing a previous *Async Shell Command* buffer if one user runs the
empty command.

I don't think this is much of a trouble for synchronous shell-command
because then it only displays the message "(Shell command succeeded with
no output)" in the minibuffer.



In GNU Emacs 31.0.50 (build 1, x86_64-unknown-openbsd7.8) of 2025-10-01
 built on computer
Repository revision: b5ea92a62b70b2cca07b3ba1d61eb6a844f1315b
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101018
System Description: OpenBSD computer 7.8 GENERIC.MP#40 amd64

Configured using:
 'configure CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib
 MAKEINFO=gmakeinfo --prefix=/home/manuel/emacs
 --bindir=/home/manuel/bin --with-x-toolkit=no
 --with-toolkit-scroll-bars=no --without-cairo --without-dbus
 --without-gconf --without-gsettings --without-compress-install'

[0001-Do-not-erase-the-output-buffer-upon-empty-command.patch (text/x-patch, attachment)]
[Message part 3 (text/plain, inline)]
-- 
Manuel Giraud

Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Sat, 11 Oct 2025 08:52:02 GMT) Full text and rfc822 format available.

Notification sent to Manuel Giraud <manuel <at> ledu-giraud.fr>:
bug acknowledged by developer. (Sat, 11 Oct 2025 08:52:02 GMT) Full text and rfc822 format available.

Message #10 received at 79560-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Manuel Giraud <manuel <at> ledu-giraud.fr>
Cc: 79560-done <at> debbugs.gnu.org
Subject: Re: bug#79560: [PATCH] Do not erase the output buffer upon empty
 command
Date: Sat, 11 Oct 2025 11:50:52 +0300
> From: Manuel Giraud <manuel <at> ledu-giraud.fr>
> Date: Fri, 03 Oct 2025 08:47:29 +0200
> 
> This patch prevents running an asynchronous empty command.  Should the
> user mistakenly enter "M-& <RET>", it won't create and pop up an empty
> *Async Shell Command* buffer.  It also has the nice property of not
> erasing a previous *Async Shell Command* buffer if one user runs the
> empty command.
> 
> I don't think this is much of a trouble for synchronous shell-command
> because then it only displays the message "(Shell command succeeded with
> no output)" in the minibuffer.

Thanks, installed on the master branch, and closing the bug.




This bug report was last modified 26 days ago.

Previous Next


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