From: Eli Zaretskii <eliz@gnu.org>
To: 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 15:46:42 +0300 [thread overview]
Message-ID: <83wo028aq5.fsf@gnu.org> (raw)
In-Reply-To: <83blhea460.fsf@gnu.org> (message from Eli Zaretskii on Wed, 07 Oct 2020 10:25:27 +0300)
> Date: Wed, 07 Oct 2020 10:25:27 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 43835@debbugs.gnu.org
>
> > I haven't yet rebuilt with --enable-checking='yes,glyphs', but I just
> > made a new, perhaps relevant, observation: after step 8 of the recipe,
> > i.e. with point at the end of the line but hscrolling undone, if I move
> > the mouse pointer to a position that pops up a tooltip (i.e., over a
> > tool-bar icon or a mode-line element), then with
> > x-gtk-use-system-tooltips set to t nothing changes but with
> > x-gtk-use-system-tooltips set to nil, the hscroll is restored, like with
> > `M-x' before `C-g', and the hscroll stays when I move the mouse so that
> > the tooltip vanishes, but if I then type `C-g', the hscroll is undone
> > again (and point remains at the end of the line, out of view).
>
> I think popping up the native tooltip has the same effect as typing
> M-x: both trigger a thorough redisplay cycle. The more important fact
> is that C-g "breaks" the display again, which is... unexpected.
Could the reason for this problem somehow be related to
gnus-horizontal-recenter, which is called by gnus-recenter basically
whenever you do something in the summary buffer? If you disable this
horizontal recentering (e.g., by setting gnus-auto-center-summary to
the value 'vertical'), does the problem go away?
next prev parent reply other threads:[~2020-10-07 12:46 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 [this message]
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=83wo028aq5.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).