all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 31653@debbugs.gnu.org, mhw@netris.org
Subject: bug#31653: 26.1; comint-scroll-show-maximum-output nil regression
Date: Wed, 30 May 2018 09:56:49 +0300	[thread overview]
Message-ID: <53501D62-2054-4AEC-B2B9-2A2666A81BD7@gnu.org> (raw)
In-Reply-To: <87k1rlbsaq.fsf@netris.org>

On May 30, 2018 8:56:13 AM GMT+03:00, Mark H Weaver <mhw@netris.org> wrote:
> Emacs 26.1 has introduced a regression compared with 25.3 in the
> handling of 'comint-scroll-show-maximum-output', which I prefer to set
> to nil.  Here's how to reproduce the problem:
> 
> * Run "emacs-26.1 -Q", with or without "-nw" as you prefer.
> * M-x shell
> * M-: (setq comint-scroll-show-maximum-output nil)
> * Press RET repeatedly until the window starts scrolling.
> 
> Observe that after the point reaches the bottom of the window, it is
> subsequently kept at the bottom of the window by aggressively
> scrolling
> one line at a time.
> 
> If you perform the same steps above with emacs-25.3, you'll see that
> it
> always recenters, so that scrolling occurs only once for every ~N/2
> lines of output, where N is the window height.
> 
> Note that (setq comint-scroll-show-maximum-output nil) still has some
> effect.  After performing the steps above, try this:
> 
> * C-l
> * Press RET repeatedly until the window starts scrolling.
> * M-: (setq comint-scroll-show-maximum-output t)
> * C-l
> * Press RET just once.
> 
> Observe that with 'comint-scroll-show-maximum-output' set to t, the
> first RET after C-l immediately scrolls the window to show the maximum
> output.
> 
> If you can suggest a workaround or a patch to fix this issue, I would
> be
> grateful.
> 
> Thanks very much for your work on Emacs.
> 
>      Mark

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.

If you are interested in the reasons for the change, see the log
message of commit d7ac7b15ca9, it points to the relevant discussion.

(This should have been in NEWS, sigh...)





  reply	other threads:[~2018-05-30  6: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 [this message]
2018-05-30  7:56   ` Mark H Weaver
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=53501D62-2054-4AEC-B2B9-2A2666A81BD7@gnu.org \
    --to=eliz@gnu.org \
    --cc=31653@debbugs.gnu.org \
    --cc=mhw@netris.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.