From: Juri Linkov <juri@linkov.net>
To: sbaugh@catern.com
Cc: Spencer Baugh <sbaugh@janestreet.com>,
Eli Zaretskii <eliz@gnu.org>,
62958@debbugs.gnu.org
Subject: bug#62958: [PATCH] Set PAGER=cat in comint.el
Date: Wed, 10 May 2023 19:39:12 +0300 [thread overview]
Message-ID: <86y1lw4mjr.fsf@mail.linkov.net> (raw)
In-Reply-To: <874jol1rml.fsf@catern.com> (sbaugh@catern.com's message of "Tue, 09 May 2023 14:55:31 +0000 (UTC)")
>> Sorry, I don't understand: why would it matter that a program produces
>> its output immediately when that output is redirected to an Emacs
>> buffer? Whatever the amount of output, the user can always page
>> through it interactively and conveniently using the normal movement
>> commands, no? What am I missing?
>
> If the command produces a lot of output it can take a long time to run
> and slow down Emacs.
I will definitely customize the new option 'comint-pager' to "cat"
as soon as it arrives to master. But for such cases when some
commands produce too long output, would it be also possible
to provide an additional option to set the number of lines
to output before stopping?
It seems not possible just to set the ENV variable 'LINES'.
From 'man less':
LINES Sets the number of lines on the screen. Takes precedence over the number of
lines specified by the TERM variable. (But if you have a windowing system
which supports TIOCGWINSZ or WIOCGETD, the window system's idea of the screen
size takes precedence over the LINES and COLUMNS environment variables.)
And indeed it has no effect when I tried. Maybe because window size
adjustments are explicitly coded in 'window--adjust-process-windows'.
next prev parent reply other threads:[~2023-05-10 16:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 21:57 bug#62958: [PATCH] Set PAGER=cat in comint.el Spencer Baugh
2023-04-20 6:43 ` Eli Zaretskii
2023-04-20 15:47 ` Spencer Baugh
2023-04-20 15:56 ` Eli Zaretskii
2023-04-20 16:01 ` Spencer Baugh
2023-05-05 6:35 ` Eli Zaretskii
2023-05-08 19:38 ` Spencer Baugh
2023-05-09 5:08 ` Eli Zaretskii
2023-05-09 14:55 ` sbaugh
2023-05-09 15:46 ` Eli Zaretskii
2023-05-09 16:30 ` Spencer Baugh
2023-05-09 16:43 ` Eli Zaretskii
2023-05-09 16:53 ` Spencer Baugh
2023-05-09 16:59 ` Eli Zaretskii
2023-05-09 17:01 ` Spencer Baugh
2023-05-09 17:05 ` Eli Zaretskii
2023-05-09 17:13 ` Spencer Baugh
2023-05-09 18:58 ` Eli Zaretskii
2023-05-16 19:49 ` Spencer Baugh
2023-05-17 11:32 ` Eli Zaretskii
2023-05-17 14:55 ` Spencer Baugh
2023-05-19 6:09 ` Eli Zaretskii
2023-05-26 11:31 ` Eli Zaretskii
2023-05-09 17:03 ` Eli Zaretskii
2023-05-10 16:39 ` Juri Linkov [this message]
2023-05-10 16:59 ` Eli Zaretskii
2023-05-10 18:13 ` Gregory Heytings
2023-05-12 17:49 ` Juri Linkov
2023-05-12 22:21 ` Gregory Heytings
2023-04-26 7:54 ` Philip Kaludercic
2023-04-26 9:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y1lw4mjr.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=62958@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sbaugh@catern.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 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.