From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: ahyatt@gmail.com, 5718@debbugs.gnu.org, gavenkoa@gmail.com
Subject: bug#5718: scroll-margin in buffer with small line count.
Date: Thu, 11 Aug 2016 18:28:32 +0300 [thread overview]
Message-ID: <83fuqbfhpb.fsf@gnu.org> (raw)
In-Reply-To: <87mvkjy0l5.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Date: Thu, 11 Aug 2016 08:03:18 -0400
> Cc: 5718@debbugs.gnu.org, Oleksandr Gavenko <gavenkoa@gmail.com>
>
> >> lines real-scroll-margin
> >> 3,4,5,6 1
> >> 7,8,9,10 2
> >> 11,12,13,14 3
> >>>15 4
> >>
> >> I count from 3 as when try make less lines Emacs warn.
> >>
> >> I think that whose modify scroll-margin want to see as many
> >> as possible margin value up to its customization value.
> >>
> >> This formula produce such values:
> >>
> >> best-scroll-margin = min( (line_count - 1)/2, scroll-margin)
> >>
> >> So previous table changed to:
> >>
> >> lines best-scroll-margin
> >> 3,4 1
> >> 5,6 2
> >> 7,8 3
> >>>9 4
> >>
> >> Also as you can see in proposal case
> >> user switch start work from 9 lines in window, not 15!
> >>
> >> Please implement described behaviour.
> >
> > I'm having a hard time understanding this report. However, it seems
> > like more like a wishlist request than a bug: you want to change the
> > scrolling behavior. I'm going to change this to wishlist for now, but
> > let me know if I've misunderstood, please.
>
> I think the complaint is that the `scroll-margin' effective value is
> capped at a 1/4 of the window height, as seen in this
> window_scroll_pixel_based (window.c):
>
> this_scroll_margin = max (0, scroll_margin);
> this_scroll_margin
> = min (this_scroll_margin, window_total_lines / 4);
Which reveals a subtle bug: the actual scroll margin should be 1 for 7
lines, 2 for 11, etc. The problem is that the value of
window_total_lines includes the mode line, which it shouldn't. Maybe
this should be fixed.
> Whereas, it seems more logical to cap it at half window height.
No, I think it would leave too few lines for moving the cursor. This
has been Emacs behavior since time immemoriam, so if we want to have a
different behavior, it should be implemented an opt-in option, not the
default.
next prev parent reply other threads:[~2016-08-11 15:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 17:26 bug#5718: scroll-margin in buffer with small line count Oleksandr Gavenko
2016-08-11 4:11 ` Andrew Hyatt
2016-08-11 12:03 ` npostavs
2016-08-11 13:05 ` Oleksandr Gavenko
2016-08-11 13:24 ` Noam Postavsky
2016-08-12 7:54 ` Oleksandr Gavenko
2016-08-11 15:28 ` Eli Zaretskii [this message]
2016-08-13 22:01 ` npostavs
2016-08-14 2:36 ` Eli Zaretskii
2016-09-11 20:58 ` npostavs
2016-09-12 6:19 ` martin rudalics
2016-09-14 2:23 ` npostavs
2016-09-14 5:30 ` martin rudalics
2016-09-12 17:36 ` Eli Zaretskii
2016-09-14 2:40 ` npostavs
2016-09-14 17:26 ` Eli Zaretskii
2017-01-03 0:48 ` npostavs
2017-01-07 8:17 ` Eli Zaretskii
2017-01-14 4:18 ` npostavs
2017-01-14 7:58 ` Eli Zaretskii
2017-01-15 21:43 ` npostavs
2017-01-16 17:08 ` Eli Zaretskii
2017-01-21 18:46 ` npostavs
2017-01-21 19:17 ` Eli Zaretskii
2017-01-22 17:21 ` npostavs
2017-01-22 17:58 ` Eli Zaretskii
2017-01-29 0:57 ` npostavs
2017-01-30 15:29 ` Eli Zaretskii
2017-01-31 4:52 ` npostavs
2017-01-31 15:33 ` Eli Zaretskii
2017-02-03 2:40 ` npostavs
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=83fuqbfhpb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5718@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=gavenkoa@gmail.com \
--cc=npostavs@users.sourceforge.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).