From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 43835@debbugs.gnu.org
Subject: bug#43835: 28.0.50; auto-hscroll-mode/current-line + show-paren-mode + gnus-summary-mode = bug
Date: Wed, 07 Oct 2020 10:08:23 +0300 [thread overview]
Message-ID: <83h7r6a4yg.fsf@gnu.org> (raw)
In-Reply-To: <87h7r7nmqx.fsf@gmx.net> (message from Stephen Berman on Tue, 06 Oct 2020 22:05:42 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 43835@debbugs.gnu.org
> Date: Tue, 06 Oct 2020 22:05:42 +0200
>
> > 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
An alternative would be to figure out what display-related changes
made by Gnus in that buffer affect this. Then we could use those
settings outside of Gnus to reproduce the issue.
> > 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
I'm not sure I understand: is that the correct display in this case?
If not, what is the correct display?
> but if I then type `C-g', the line scrolls back to the right and
> point is again not visible, as in step 8.
Weird...
next prev parent reply other threads:[~2020-10-07 7:08 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
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 [this message]
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=83h7r6a4yg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43835@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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).