unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43835@debbugs.gnu.org
Subject: bug#43835: 28.0.50; auto-hscroll-mode/current-line + show-paren-mode + gnus-summary-mode = bug
Date: Tue, 06 Oct 2020 22:05:42 +0200	[thread overview]
Message-ID: <87h7r7nmqx.fsf@gmx.net> (raw)
In-Reply-To: <83lfgj9nml.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Oct 2020 22:10:26 +0300")

On Tue, 06 Oct 2020 22:10:26 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Date: Tue, 06 Oct 2020 20:53:53 +0200
>>
>> I have observed a quirk in auto hscrolling the current line under
>> specific conditions.  I have only seen it in gnus-summary-mode, but
>> there can reproduce it reliably with the following recipe:
>
> Thanks, but having Gnus in the picture is too much.  Debugging
> redisplay issues involved in these momentary movements is hard as it
> is already.

I believe you, and I wish I could remove Gnus from the recipe (I've been
seeing this problem for at least three years, but only today did I
recognize that show-paren-mode was involved and so could reliably
reproduce it).

> You could perhaps help me come up with ideas if, in a build configured
> with --enable-checking='yes,glyphs', you did the following:
>
>   emacs -Q
>   M-x blink-cursor-mode RET
>   M-x global-eldoc-mode RET
>
> Then perform your recipe up to and excluding step 8.
>
>   M-x trace-redisplay RET
>
> Wait till there are no more messages printed to stderr, then perform
> step 8 and notice the messages it causes to be printed, after you type
> C-e.
>
> Then do the same experiment, but with some other buffer, where you say
> that the problem doesn't happen, and tell what messages were printed
> by trace-redisplay in that case after C-e.  If there's any difference
> between these two scenarios visible in the trace, that could give some
> ideas regarding the possible cause(s).
>
> Thanks.

Thanks for the suggestions, I'll try them as soon as I can and report back.

>> I can reproduce this problem in Emacs 26, 27 and master, but I have only
>> been able to reproduce it in Gnus summary buffers, and only on the last
>> line of the summary and only when this line is longer than window-width
>> (so that hscrolling can happen) and the line ends with a pair of paren
>> characters (brackets and braces also show the effect) and
>> show-paren-mode is enabled.  Sometimes I have seen the hscroll get
>> restored after a several seconds, but other times this does not happen
>> (though I haven't tried waiting for more than maybe 15-20 seconds).
>
> Does the hscroll get restored if you type "M-x"?

As soon as I type `M-x' I see the line scroll left and the cursor at the
end, and it remains like that, but if I then type `C-g', the line
scrolls back to the right and point is again not visible, as in step 8.

> P.S. Please remember performing all these tests with both
> blink-cursor-mode and global-eldoc-mode disabled.  Those two cause
> frequent redisplay cycles that can completely obscure the actual
> problems.

Ok.

Steve Berman





  reply	other threads:[~2020-10-06 20:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 18:53 bug#43835: 28.0.50; auto-hscroll-mode/current-line + show-paren-mode + gnus-summary-mode = bug Stephen Berman
2020-10-06 19:10 ` Eli Zaretskii
2020-10-06 20:05   ` Stephen Berman [this message]
2020-10-06 21:59     ` Stephen Berman
2020-10-07  7:25       ` Eli Zaretskii
2020-10-07 12:46         ` Eli Zaretskii
2020-10-07 12:58           ` Eli Zaretskii
2020-10-07  7:08     ` Eli Zaretskii
2020-10-07 20:54       ` Stephen Berman
2020-10-08  8:22         ` Eli Zaretskii
2020-10-08  8:39           ` Stephen Berman
2020-10-08  9:10             ` Eli Zaretskii
2020-10-08 10:18               ` Stephen Berman
2020-10-08 11:55                 ` Eli Zaretskii
2020-10-08 12:24                   ` Stephen Berman
2020-10-08 12:27                     ` Eli Zaretskii
2020-10-08 11:53               ` 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=87h7r7nmqx.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=43835@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 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).