From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: ahyatt@gmail.com, 5718@debbugs.gnu.org, gavenkoa@gmail.com
Subject: bug#5718: scroll-margin in buffer with small line count.
Date: Sun, 15 Jan 2017 16:43:34 -0500 [thread overview]
Message-ID: <87k29wxam1.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83o9zaax8x.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Jan 2017 09:58:38 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: npostavs@users.sourceforge.net
>> Cc: 5718@debbugs.gnu.org, ahyatt@gmail.com, gavenkoa@gmail.com
>> Date: Fri, 13 Jan 2017 23:18:56 -0500
>>
>> Looks like the same kind of problem as the other case, I can fix it
>> again by subtracting frame_line_height, though again, subtracting the
>> partial height is probably more correct.
>
> I think you are right on both counts. Computing the partial height of
> the last visible line shouldn't be hard, I think. Let me know if you
> need help with that.
Yeah, I'm still a bit lost in all the different structures. It seems
(it.last_visible_y % frame_line_height) might work. The matrix row
stuff in xdisp seems a more direct way of getting it, though I guess
that's not really usable from window.c? What would be the idiomatic way
of doing this?
#define MR_PARTIALLY_VISIBLE(ROW) \
((ROW)->height != (ROW)->visible_height)
By the way, in window_scroll_pixel_based (lines 5139 to 5158) the
position of "it" is saved twice, and it looks like the first one of
these can never be used (because the second overwrites it), correct?
ptrdiff_t charpos, bytepos;
bool partial_p;
/* Save our position, for the <---------------- Useless?
window_scroll_pixel_based_preserve_y case. */
charpos = IT_CHARPOS (it);
bytepos = IT_BYTEPOS (it);
/* We moved the window start towards BEGV, so PT may be now
in the scroll margin at the bottom. */
move_it_to (&it, PT, -1,
(it.last_visible_y - WINDOW_HEADER_LINE_HEIGHT (w)
- this_scroll_margin - 1 - frame_line_height),
-1,
MOVE_TO_POS | MOVE_TO_Y);
/* Save our position, in case it's correct. */
charpos = IT_CHARPOS (it);
bytepos = IT_BYTEPOS (it);
next prev parent reply other threads:[~2017-01-15 21:43 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
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 [this message]
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=87k29wxam1.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=5718@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=eliz@gnu.org \
--cc=gavenkoa@gmail.com \
/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).