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: Thu, 08 Oct 2020 10:39:38 +0200	[thread overview]
Message-ID: <87pn5tdsc5.fsf@gmx.net> (raw)
In-Reply-To: <834kn586up.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 08 Oct 2020 11:22:38 +0300")

On Thu, 08 Oct 2020 11:22:38 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: 43835@debbugs.gnu.org
>> Date: Wed, 07 Oct 2020 22:54:51 +0200
>>
>> 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.
>
> 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:

(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")
    (emacs-lisp-mode)
    (goto-char (point-min)))
  (show-paren-mode)
  (switch-to-buffer buf))

> 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:

(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)\nSubject: Re: bug#39280: 27.0.60; wdired-get-filename ignores first argument (this is a test)\nSubject: Re: bug#39280: 27.0.60; wdired-get-filename ignores first argument (this is a test)\n")
    (emacs-lisp-mode)
    (goto-char (point-min)))
  (show-paren-mode)
  (switch-to-buffer buf))

Steve Berman





  reply	other threads:[~2020-10-08  8:39 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 [this message]
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=87pn5tdsc5.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).