From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Antoine Levitt <antoine.levitt@gmail.com>, 8355@debbugs.gnu.org
Subject: bug#8355: 24.0.50; Boxes in mode-line and scrolling
Date: Tue, 08 Dec 2020 19:27:12 +0100 [thread overview]
Message-ID: <878sa8b1bz.fsf@gnus.org> (raw)
In-Reply-To: <83sg8g5fer.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 08 Dec 2020 20:19:40 +0200")
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> I don't think I understand what is the complaint here. The screen
> position of the cursor _is_ preserved with these settings, don't you
> agree? They are preserved on my system: I did many C-v and M-v, and
> the cursor stays on the same spot on display, moving a few pixels here
> and there when the line at cursor is smaller or taller than the
> default.
>
> If this is what you see, then what is NOT working as expected in this
> scenario?
I think the bug reporter means the inconsistent behaviour of point.
Start with:
[-- Attachment #2: Type: image/png, Size: 180801 bytes --]
[-- Attachment #3: Type: text/plain, Size: 24 bytes --]
And then M-v and C-v:
[-- Attachment #4: Type: image/png, Size: 187719 bytes --]
[-- Attachment #5: Type: text/plain, Size: 518 bytes --]
Note how we landed on the line over where we started.
> The original report was talking about C-v followed by M-v producing a
> 1-line displacement. Is _that_ the problem? If so, why did you
> expect Emacs to come to the same place, AFAIK there's no guarantee of
> that when variable-height text is involved.
Shouldn't there be? Going back a page and forward a page should ideally
land you on the same line.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-08 18:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 13:41 bug#8355: 24.0.50; Boxes in mode-line and scrolling Antoine Levitt
2020-12-08 15:05 ` Lars Ingebrigtsen
2020-12-08 15:56 ` Antoine Levitt
2020-12-08 18:18 ` Lars Ingebrigtsen
2020-12-08 18:29 ` Eli Zaretskii
2020-12-08 18:19 ` Eli Zaretskii
2020-12-08 18:27 ` Lars Ingebrigtsen [this message]
2020-12-08 18:33 ` Eli Zaretskii
2020-12-09 16:17 ` Eli Zaretskii
2020-12-09 17:01 ` Lars Ingebrigtsen
2020-12-09 17:13 ` Eli Zaretskii
2020-12-09 17:24 ` Lars Ingebrigtsen
2020-12-09 20:47 ` Antoine Levitt
2020-12-10 3:34 ` Eli Zaretskii
2020-12-11 8:35 ` Antoine Levitt
2020-12-11 8:47 ` Eli Zaretskii
2020-12-11 9:08 ` Antoine Levitt
2020-12-11 11:59 ` Eli Zaretskii
2020-12-11 12:25 ` Antoine Levitt
2020-12-14 18:25 ` Eli Zaretskii
2020-12-14 19:02 ` Antoine Levitt
2020-12-14 19:27 ` Eli Zaretskii
2020-12-14 18:26 ` Eli Zaretskii
2020-12-14 19:05 ` Lars Ingebrigtsen
2020-12-14 19:30 ` Eli Zaretskii
2020-12-15 5:23 ` Lars Ingebrigtsen
2021-01-20 17:09 ` Lars Ingebrigtsen
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=878sa8b1bz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=8355@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--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).