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: Thu, 08 Oct 2020 12:10:15 +0300 [thread overview]
Message-ID: <831ri984nc.fsf@gnu.org> (raw)
In-Reply-To: <87pn5tdsc5.fsf@gmx.net> (message from Stephen Berman on Thu, 08 Oct 2020 10:39:38 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 43835@debbugs.gnu.org
> Date: Thu, 08 Oct 2020 10:39:38 +0200
>
> > bidi-paragraph-direction is set to left-to-right in any descendant of
> > prog-mode, in particular in Emacs Lisp mode. And yet I couldn't
> > reproduce this in a Lisp buffer, no matter what I tried. So that
> > setting is not the only cause.
>
> Strange, because when I replace the above sexp in step 1 by the
> following, I see the same problem at step 2:
I tried reproducing the problem in a real-life .el file, not in a
synthetic example with a single Lisp line. That's why I said
bidi-paragraph-direction cannot be the only reason.
> > If you add a line of text before and after the Subject line you insert
> > in the recipe, does the problem go away? It does here. But then I
> > wonder whether this problem only happens in Gnus with the very first
> > or the very last line of the summary buffer. If that's not so, I'm
> > probably missing something else.
>
> I think I've only seen this on the last line in a Gnus summary buffer.
> This also holds for the new test case (also in Emacs Lisp mode): after
> evaluating the following sexp, I see the problem only on the last line:
OK, so I think the conditions for triggering the problem are well
understood, and we both have the same observations, thanks.
next prev parent reply other threads:[~2020-10-08 9:10 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
2020-10-08 8:22 ` Eli Zaretskii
2020-10-08 8:39 ` Stephen Berman
2020-10-08 9:10 ` Eli Zaretskii [this message]
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=831ri984nc.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).