From: Mark H Weaver <mhw@netris.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31653@debbugs.gnu.org
Subject: bug#31653: 26.1; comint-scroll-show-maximum-output nil regression
Date: Wed, 30 May 2018 03:56:47 -0400 [thread overview]
Message-ID: <8736y9bmps.fsf@netris.org> (raw)
In-Reply-To: <53501D62-2054-4AEC-B2B9-2A2666A81BD7@gnu.org> (Eli Zaretskii's message of "Wed, 30 May 2018 09:56:49 +0300")
Hi Eli,
Eli Zaretskii <eliz@gnu.org> writes:
> It's a deliberate change, by popular demand: shell-mode now sets
> scroll-conservatively to a large value locally in shell buffers. Reset
> that in your mode hook, and Bob's your uncle.
That's very helpful, thank you!
> If you are interested in the reasons for the change, see the log
> message of commit d7ac7b15ca9, it points to the relevant discussion.
Thanks for the pointer. I acknowledge that I'm in the minority here,
but I greatly prefer less frequent scrolling, so that I have more time
to visually process the text before it moves and disrupts my ability to
process it.
Ideally, both settings of 'comint-scroll-show-maximum-output' would
behave as expected, without mode hooks.
That said, I don't have time to work on this myself, and it's certainly
of very little importance. The mode hook workaround is good enough for
me, and I guess there are very few people with my preferences, so I'm
willing to let this go. Feel free to close this bug as "wontfix", or to
keep it open, as you prefer.
Thanks again,
Mark
next prev parent reply other threads:[~2018-05-30 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 5:56 bug#31653: 26.1; comint-scroll-show-maximum-output nil regression Mark H Weaver
2018-05-30 6:56 ` Eli Zaretskii
2018-05-30 7:56 ` Mark H Weaver [this message]
2018-05-30 16:48 ` Eli Zaretskii
2018-06-01 9:26 ` Eli Zaretskii
2018-05-30 8:01 ` Andreas Schwab
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=8736y9bmps.fsf@netris.org \
--to=mhw@netris.org \
--cc=31653@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.