From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Spencer Baugh <sbaugh@janestreet.com>
Cc: 72426@debbugs.gnu.org
Subject: bug#72426: 29.2.50; comint-pager doesn't affect async-shell-command
Date: Tue, 6 Aug 2024 09:29:34 -0700 [thread overview]
Message-ID: <091182cc-9667-7740-9712-9affe3a2548e@gmail.com> (raw)
In-Reply-To: <864j7xpsc9.fsf@gnu.org>
On 8/6/2024 8:46 AM, Eli Zaretskii wrote:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Cc: 72426@debbugs.gnu.org
>> Date: Tue, 06 Aug 2024 11:33:47 -0400
>>
>> Anyway, can we just remove comint-pager for now, to avoid adding
>> something broken that has to be maintained? I can try it again for
>> Emacs 31.
>
> I think it's too late for that, sorry. It is already supported in
> Eshell, and Emacs 30 is frozen for such changes anyway.
For what it's worth, from the perspective of Eshell, I see the current
implementation as a half-measure that makes things better, but may be
obviated by a better implementation (e.g. setting PAGER in startup.el).
While it's disappointing to have a not-quite-right solution make it to
30.1, I don't think that solution paints us into a corner either: it
doesn't make it any harder for us to make the startup.el change for 31.1.
On the plus(?) side, it looks like the only place 'comint-pager' is
mentioned is in the Eshell manual (and the docstrings, of course). So
since we're not really "advertising" this option, and since I think it
would still be useful even with the startup.el change, I don't think we
have to worry too much. We can just consider the underlying issue to be
something we'll (try to) fix in 31.
next prev parent reply other threads:[~2024-08-06 16:29 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 [this message]
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
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=091182cc-9667-7740-9712-9affe3a2548e@gmail.com \
--to=jporterbugs@gmail.com \
--cc=72426@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).