From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: antoine.levitt@gmail.com, 8355@debbugs.gnu.org
Subject: bug#8355: 24.0.50; Boxes in mode-line and scrolling
Date: Mon, 14 Dec 2020 20:26:23 +0200 [thread overview]
Message-ID: <83o8iwb5ww.fsf@gnu.org> (raw)
In-Reply-To: <87czziyjsc.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 09 Dec 2020 18:24:35 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: antoine.levitt@gmail.com, 8355@debbugs.gnu.org
> Date: Wed, 09 Dec 2020 18:24:35 +0100
>
> (defun make-buffer ()
> (switch-to-buffer "*images*")
> (erase-buffer)
> (let ((height (* (frame-pixel-height) 0.6))
> (width (* (frame-pixel-width) 0.7)))
> (dotimes (i 10)
> (let ((svg (svg-create width height)))
> (svg-rectangle svg 0 0 width height
> :fill (format "#%02x%02x%02x"
> (random 255)
> (random 255)
> (random 255)))
> (svg-text svg (format "Image %d" i)
> :font-size 50
> :fill "black"
> :font-weight "bold"
> :x (/ width 2)
> :y (/ height 2)
> :text-anchor "middle")
> (insert-image (svg-image svg :scale 1))
> (insert (format "\n\nImage %d\n\n" i))))))
>
> Scroll downwards to the test "Image 4", for instance. This is what I
> have in my window then:
>
> So we see the entirety of Image 4, and the top of Image 5, and that's
> fine. Then hit `M-v':
>
> We see the entirety of image 2, and the top of image 3, which seems like
> we've overshot -- I'd expect to see the entirety of image 3, and the top
> of image 4.
>
> Then C-v:
>
> We're not back to where we started, but instead have the entirety of
> image 3, and the top of image 4 (which is what I'd expect when C-v-ing
> from where I was).
>
> So I think Emacs behaves very nicely when C-v-ing down a buffer of large
> images, but when M-v-ing back up, it seems to scroll too far.
Thanks, this should now be fixed on the master branch.
next prev parent reply other threads:[~2020-12-14 18:26 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
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 [this message]
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=83o8iwb5ww.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8355@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--cc=larsi@gnus.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).