From: Eliza Velasquez <eliza@eliza.sh>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, 64394@debbugs.gnu.org
Subject: bug#64394: [PATCH] Fix `async-shell-command-display-buffer' display
Date: Sat, 01 Jul 2023 01:42:53 -0700 [thread overview]
Message-ID: <87edls6n02.fsf@eliza.sh> (raw)
In-Reply-To: <83v8f4qcdd.fsf@gnu.org>
On Sat, Jul 01 2023 at 11:12 +03, Eli Zaretskii <eliz@gnu.org> wrote:
> But that's exactly what this variable is about, AFAIU:
>
> Whether to display the command buffer immediately.
> If t, display the buffer immediately; if nil, wait until there
> is output.
>
> Note the last part.
>
> So why do you think this behavior is a problem?
On a philosophical level: It's surprising to me in that previous example
that if `async-shell-command-display-buffer' is t, the buffer is /not/
displayed (according to `display-buffer-alist'), but if it's nil, it
/is/ displayed, eventually (ignoring `display-buffer-alist').
On a practical level: The user may want to differentiate buffer display
behavior based on the name of the shell command buffer or by some other
predicate, including disabling showing that buffer, regardless of
whether `async-shell-command-display-buffer' is set to t or nil. I have
recently authored a package to make this easier [1] and ran into this
problem. The example configuration in the README might shed some more
light on the expected behavior.
[1] https://github.com/elizagamedev/shell-command-x.el
--
Eliza
next prev parent reply other threads:[~2023-07-01 8:42 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
2023-07-01 7:52 ` Eliza Velasquez
2023-07-01 8:12 ` Eli Zaretskii
2023-07-01 8:42 ` Eliza Velasquez [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edls6n02.fsf@eliza.sh \
--to=eliza@eliza.sh \
--cc=64394@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.