From: Eli Zaretskii <eliz@gnu.org>
To: Eliza Velasquez <eliza@eliza.sh>, martin rudalics <rudalics@gmx.at>
Cc: 64394@debbugs.gnu.org
Subject: bug#64394: [PATCH] Fix `async-shell-command-display-buffer' display
Date: Sat, 01 Jul 2023 10:24:05 +0300 [thread overview]
Message-ID: <833528rt62.fsf@gnu.org> (raw)
In-Reply-To: <873528cuoe.fsf@eliza.sh> (message from Eliza Velasquez on Fri, 30 Jun 2023 18:00:33 -0700)
> From: Eliza Velasquez <eliza@eliza.sh>
> Date: Fri, 30 Jun 2023 18:00:33 -0700
>
> If `async-shell-command-display-buffer' was nil, it did not respect
> `display-buffer-alist' entries with `display-buffer-no-window'. This
> behavior has been fixed.
I'm probably missing something, but how can display-buffer fail to
support any action function, such as display-buffer-no-window?
Martin, what am I missing here?
> For example, I never want to see any shell command buffers with no
> output, and I also never want to see any shell command buffers named
> `*shell:mpv*'.
That's fine, but those are your preferences. I'd feel uncomfortable
with forcing them on everyone, if we already have a way of tailoring
this behavior by user customizations.
next prev parent reply other threads:[~2023-07-01 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 1:00 bug#64394: [PATCH] Fix `async-shell-command-display-buffer' display Eliza Velasquez
2023-07-01 7:24 ` Eli Zaretskii [this message]
2023-07-01 7:52 ` Eliza Velasquez
2023-07-01 8:12 ` Eli Zaretskii
2023-07-01 8:42 ` Eliza Velasquez
2023-07-02 7:09 ` martin rudalics
2023-07-02 18:03 ` Juri Linkov
2023-07-03 6:46 ` martin rudalics
2023-07-04 1:18 ` Eliza Velasquez
2023-07-04 17:54 ` Juri Linkov
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=833528rt62.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64394@debbugs.gnu.org \
--cc=eliza@eliza.sh \
--cc=rudalics@gmx.at \
/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).