From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: sbaugh@janestreet.com, 72426@debbugs.gnu.org
Subject: bug#72426: 29.2.50; comint-pager doesn't affect async-shell-command
Date: Wed, 07 Aug 2024 14:51:24 +0300 [thread overview]
Message-ID: <86bk24o8jn.fsf@gnu.org> (raw)
In-Reply-To: <f6120ffb-cbc5-eda6-51c6-e627c02626cc@gmail.com> (message from Jim Porter on Tue, 6 Aug 2024 19:36:15 -0700)
> Date: Tue, 6 Aug 2024 19:36:15 -0700
> Cc: 72426@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> Just to be extra-sure, I tried using 'async-shell-command' to run "git
> log" with PAGER unset, and sure enough it tried to use "less" for
> paging, which didn't go very well. "PAGER=cat" was much better.
Did you try with process-connection-type nil?
next prev parent reply other threads:[~2024-08-07 11:51 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 [this message]
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=86bk24o8jn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72426@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--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).