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: 27008@debbugs.gnu.org
Subject: bug#27008: 26.0.50; auto-hscroll-mode and scroll-left
Date: Wed, 31 May 2017 16:18:26 +0200	[thread overview]
Message-ID: <87efv52jpp.fsf@rosalinde> (raw)
In-Reply-To: <834lw1ebvi.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 May 2017 10:14:41 +0300")

On Wed, 31 May 2017 10:14:41 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: 27008@debbugs.gnu.org
>> Date: Tue, 30 May 2017 21:45:47 +0200
>> 
>> Thanks.  Yes, with this patch the non-current lines are displayed from
>> w->min_hscroll.  However, there's a new problem: now when points moves
>> to a line, that line automatically scrolls further by w->min_hscroll.
>> So when I do `(scroll-left 32 t)' and then move point to another line,
>> that line scrolls further left so that its column 64 is on the left edge
>> of the window (the other lines remain displayed starting at column 32).
>> When point moves to the next line, that one scrolls further to column 64
>> and the previous one goes back to being displayed from column 32.
>
> Does the below (to be applied on top of current master, i.e. first
> revert the previous patch) fix this?

Yes, the display and the horizontal scrolling is now exactly as I hoped
it would be; many thanks!  

There is one minor issue: with auto-hscroll-mode set to `current-line'
and (scroll-left 32 t), when I scroll vertically by holding down <down>
or C-n or <up> or C-p, the motion is less smooth than usual.  With the
same auto-hscroll-mode setting but no scroll-left, vertical scrolling is
smoother, but still not as smooth as with auto-hscroll-mode set to t or
nil (with either of these settings, vertical scrolling seems slightly
less smooth with (scroll-left 32 t) than with no scroll-left, though the
difference is less noticeable than with auto-hscroll-mode set to
current-line).  But I don't think this is a serious annoyance, so unless
you see an easy fix for it, I think you should commit the patch as is to
master.

Steve Berman





  reply	other threads:[~2017-05-31 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 14:10 bug#27008: 26.0.50; auto-hscroll-mode and scroll-left Stephen Berman
2017-05-21 15:23 ` Eli Zaretskii
2017-05-21 20:12   ` Stephen Berman
2017-05-30 14:56     ` Eli Zaretskii
2017-05-30 16:57       ` Stephen Berman
2017-05-30 17:18         ` Eli Zaretskii
2017-05-30 17:31           ` Eli Zaretskii
2017-05-30 19:45             ` Stephen Berman
2017-05-31  7:14               ` Eli Zaretskii
2017-05-31 14:18                 ` Stephen Berman [this message]
2017-05-31 14:39                   ` Eli Zaretskii
2017-05-31 16:04                     ` 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=87efv52jpp.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=27008@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).