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: Wed, 07 Oct 2020 22:54:51 +0200 [thread overview]
Message-ID: <87eem9n4dg.fsf@gmx.net> (raw)
In-Reply-To: <83h7r6a4yg.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 07 Oct 2020 10:08:23 +0300")
On Wed, 07 Oct 2020 10:08:23 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> 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.
I figured it out and you may be surprised. Here's the new recipe:
0. emacs -Q
1. Evaluate the following sexp:
(let ((buf (get-buffer-create "*test*")))
(with-current-buffer buf
(setq auto-hscroll-mode 'current-line
truncate-lines t
bidi-paragraph-direction 'left-to-right)
(insert "Subject: Re: bug#39280: 27.0.60; wdired-get-filename ignores first argument (this is a test)\n")
(goto-char (point-min)))
(show-paren-mode)
(switch-to-buffer buf))
2. Now typing `C-e' shows the problem.
The settings of truncate-lines and bidi-paragraph-direction come from
gnus-summary-mode, the newline at the end of the inserted text is also
essential (I think I had omitted that when I though I couldn't replicate
the problem in another buffer).
Do you still want the output of trace-redisplay?
Steve Berman
next prev parent reply other threads:[~2020-10-07 20:54 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
2020-10-07 20:54 ` Stephen Berman [this message]
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=87eem9n4dg.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).