From: Eli Zaretskii <eliz@gnu.org>
To: Reza Shafiei <joghd1988@outlook.com>
Cc: 61100@debbugs.gnu.org
Subject: bug#61100: 29.0.60; `shell-command' displays all of *Shell Command Output* in the minibuffer
Date: Fri, 27 Jan 2023 19:03:01 +0200 [thread overview]
Message-ID: <83zga3c3lm.fsf@gnu.org> (raw)
In-Reply-To: <PA4P189MB131167BA9637FB61B648CAA2BACC9@PA4P189MB1311.EURP189.PROD.OUTLOOK.COM> (message from Reza Shafiei on Fri, 27 Jan 2023 15:16:01 +0000)
> From: Reza Shafiei <joghd1988@outlook.com>
> Date: Fri, 27 Jan 2023 15:16:01 +0000
> msip_labels:
>
> I apologize in advance for any mistakes since English is not my native
> language and it is the first time that I report a bug.
>
> How to reproduce:
> 1) emacs -Q
> 2) (setq shell-command-dont-erase-buffer t)
> 3) M-! with some command that generates short output, like
> M-! echo "foo". Output is displayed in the minibuffer:
> ----------------
> foo
> ----------------
> 4) M-! with another command that also generates short output,
> like M-! echo "bar". You will see that the output of previous
> commands is also displayed again in the minibuffer:
> ----------------
> foo
> bar
> ----------------
>
> `shell-command-on-region' has the same behavior.
>
> What I understand form the documentation of these two commands is
> that only the output of the most recent command should be
> displayed in the minibuffer (if it is short of course), not the
> entire content of *Shell Command Output*.
Thanks.
The documentation describes the default situation, where
shell-command-dont-erase-buffer is not customized.
I've now updated the documentation to describe this effect of
customizing that variable. I think this fixes the discrepancy.
next prev parent reply other threads:[~2023-01-27 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 15:16 bug#61100: 29.0.60; `shell-command' displays all of *Shell Command Output* in the minibuffer Reza Shafiei
2023-01-27 17:03 ` Eli Zaretskii [this message]
2023-01-27 19:15 ` Reza Shafiei
2023-01-27 19:56 ` Eli Zaretskii
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=83zga3c3lm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61100@debbugs.gnu.org \
--cc=joghd1988@outlook.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).