unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 14:55:58 +0300	[thread overview]
Message-ID: <83y2kh6iep.fsf@gnu.org> (raw)
In-Reply-To: <87lfghdnqo.fsf@gmx.net> (message from Stephen Berman on Thu, 08 Oct 2020 12:18:55 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 43835@debbugs.gnu.org
> Date: Thu, 08 Oct 2020 12:18:55 +0200
> 
> I can see the problem is a real .el file, but it seems to depend on the
> form of the line and other conditions I don't understand.  I visited
> bindings.el and added the following line (with no line break, in case
> one gets added to it in the email) at the end of the file:

Like I said: this happens when the problematic line is either the very
first or the very last line of the buffer.  I think you are describing
the latter situation?

> (setq bla "Subject: Re: bug#39280: 27.0.60; wdired-get-filename ignores first argument")
> 
> Then I added a newline, evaluated (setq auto-hscroll-mode 'current-line
> truncate-lines t) and enabled show-paren-mode.  With point at the
> beginning of the above line I typed `C-e' and the line scrolled left and
> the end of the line remained visible, i.e., no problem.  Then I deleted
> the final `)', typed `C-a C-e' and the line scrolled left and then
> immediately undid the hscroll so the end of the line was not visible but
> after a fraction of a second it scrolled left again and the end of the
> line remained visible.  Then I additionally deleted the final `"', typed
> `C-a C-e' and the line scrolled left and now the end of the line
> remained out of view indefinitely.  This even though the final line does
> now does not end with a parenthesis group, in contrast to all previous
> cases where I've seen the problem.  And indeed, if I restart the
> experiment in a fresh emacs -Q and insert just `(setq bla "Subject: Re:
> bug#39280: 27.0.60; wdired-get-filename ignores first argument' --
> i.e. without the closing `")' -- plus a newline and make the other
> necessary settings, then I see no hscrolling problem.  Can you replicate
> these observations?

I don't see them after fixing the problem.  Is it still necessary to
see if they existed before the fix?

Thanks.





  reply	other threads:[~2020-10-08 11:55 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
2020-10-08 10:18               ` Stephen Berman
2020-10-08 11:55                 ` Eli Zaretskii [this message]
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=83y2kh6iep.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).