From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: sbaugh@janestreet.com, 72426@debbugs.gnu.org
Subject: bug#72426: 29.2.50; comint-pager doesn't affect async-shell-command
Date: Fri, 13 Sep 2024 09:08:54 +0300 [thread overview]
Message-ID: <86zfocjdah.fsf@gnu.org> (raw)
In-Reply-To: <facdaabb-bdd0-445c-87ca-697603dc0b37@gutov.dev> (message from Dmitry Gutov on Fri, 13 Sep 2024 04:17:11 +0300)
> Date: Fri, 13 Sep 2024 04:17:11 +0300
> Cc: 72426@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 03/08/2024 18:38, Eli Zaretskii wrote:
> >> comint-terminfo-terminal affects async-shell-command, why not this?
> > Ugh! A mistake, IMNSHO. But that ship sailed a long time ago, so we
> > cannot fix the mistake. We can avoid enlarging the mistake, though.
> >
> >> If the fact that the variable is in comint is the problem, I can rename it and move it elsewhere.
> > I don't think functions that are almost primitives should pay
> > attention to application-level features such as this one.
>
> FWIW async-shell-command's behavior is affected by a bunch of other
> comint-* variables as well because it uses a major mode which inherits
> from comint-mode (previously it was shell-mode, now shell-command-mode,
> but that aspect didn't change).
Yes, and that is baaad!
next prev parent reply other threads:[~2024-09-13 6:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 18:35 bug#72426: 29.2.50; comint-pager doesn't affect async-shell-command Spencer Baugh
2024-08-02 18:39 ` Spencer Baugh
2024-08-03 5:48 ` Eli Zaretskii
2024-08-03 10:47 ` Spencer Baugh
2024-08-03 15:38 ` Eli Zaretskii
2024-08-03 16:42 ` Spencer Baugh
2024-08-03 17:18 ` Eli Zaretskii
2024-08-06 15:33 ` Spencer Baugh
2024-08-06 15:46 ` Eli Zaretskii
2024-08-06 16:29 ` Jim Porter
2024-08-06 18:02 ` Eli Zaretskii
2024-08-03 18:38 ` Jim Porter
2024-08-06 15:31 ` Spencer Baugh
2024-08-06 15:50 ` Eli Zaretskii
2024-08-06 16:42 ` Spencer Baugh
2024-08-06 18:07 ` Eli Zaretskii
2024-08-06 18:49 ` Spencer Baugh
2024-08-06 19:07 ` Eli Zaretskii
2024-08-06 19:23 ` Spencer Baugh
2024-08-07 2:36 ` Jim Porter
2024-08-07 11:51 ` Eli Zaretskii
2024-08-07 15:05 ` Spencer Baugh
2024-08-07 15:26 ` Eli Zaretskii
2024-08-07 15:31 ` Spencer Baugh
2024-08-07 16:08 ` Jim Porter
2024-08-07 11:18 ` Eli Zaretskii
2024-08-07 15:09 ` Spencer Baugh
2024-08-17 9:25 ` Eli Zaretskii
2024-09-13 1:17 ` Dmitry Gutov
2024-09-13 6:08 ` Eli Zaretskii [this message]
2024-09-13 23:45 ` Dmitry Gutov
2024-09-14 6:27 ` 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=86zfocjdah.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72426@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=sbaugh@janestreet.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).