From: Reza Shafiei <joghd1988@outlook.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "61100@debbugs.gnu.org" <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:15:24 +0000 [thread overview]
Message-ID: <PA4P189MB1311062AC60768B86E889590BACC9@PA4P189MB1311.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <83zga3c3lm.fsf@gnu.org>
> From: Eli Zaretskii <eliz@gnu.org>
>
> I've now updated the documentation to describe this effect of
> customizing that variable. I think this fixes the discrepancy.
Yes, it does. Thanks.
But is it really the intended/expected behavior? I thought it is not;
that's why I reported it. I customize shell-command-dont-erase-buffer
because I like to be able to see and compare the output of different
commands in *Shell Command Output*, and refer to them later.
If it is the intended behavior, then now the documentation clarifies it.
Thanks again.
next prev parent reply other threads:[~2023-01-27 19:15 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
2023-01-27 19:15 ` Reza Shafiei [this message]
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=PA4P189MB1311062AC60768B86E889590BACC9@PA4P189MB1311.EURP189.PROD.OUTLOOK.COM \
--to=joghd1988@outlook.com \
--cc=61100@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).