From: Spencer Baugh <sbaugh@janestreet.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, 72426@debbugs.gnu.org
Subject: bug#72426: 29.2.50; comint-pager doesn't affect async-shell-command
Date: Tue, 06 Aug 2024 14:49:45 -0400 [thread overview]
Message-ID: <ierttfx32ra.fsf@janestreet.com> (raw)
In-Reply-To: <86v80do795.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Aug 2024 21:07:02 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Cc: jporterbugs@gmail.com, 72426@debbugs.gnu.org
>> Date: Tue, 06 Aug 2024 12:42:09 -0400
>>
>> --- a/lisp/startup.el
>> +++ b/lisp/startup.el
>> @@ -854,6 +854,10 @@ normal-top-level
>> ;; We are careful to do it late (after term-setup-hook), although the
>> ;; new multi-tty code does not use $TERM any more there anyway.
>> (setenv "TERM" "dumb")
>> + ;; Likewise, subprocesses should not use a pager unless told
>> + ;; otherwise, since it generally won't work.
>> + (when (executable-find "cat")
>> + (setenv "PAGER" "cat"))
>
> We need to work on the comment, because it doesn't explain any of what
> it needs to. Worse, it says something very confusing and at least
> inaccurate.
Could you just say what you'd prefer the comment to be? I'm not sure
what exactly you'd like it to explain.
next prev parent reply other threads:[~2024-08-06 18:49 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 [this message]
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=ierttfx32ra.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=72426@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.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).