From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: 67533@debbugs.gnu.org
Subject: bug#67533: SVG images confound position pixel measurements
Date: Sun, 03 Dec 2023 18:33:05 +0200 [thread overview]
Message-ID: <83fs0j6ybi.fsf@gnu.org> (raw)
In-Reply-To: <DAB445D2-03C1-4E23-9EAA-BA422D42614F@gmail.com> (message from JD Smith on Sun, 3 Dec 2023 10:49:37 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sun, 3 Dec 2023 10:49:37 -0500
>
> BTW, in case anyone is wondering where window-text-pixel-size with a negative pixel FROM offset is needed, Po Lu's pixel-scroll-precision-up-page is using precisely this approach to measure the content above window-start (so as to smoothly scroll up with high performance):
>
> (let* ((start (window-start))
> (dims (window-text-pixel-size nil (cons start (- delta))
> start nil nil nil t))
>
I know very well why that feature was added. My questions was not
about negative offsets in general, but about negative offsets when
FROM is in the first line of the buffer, i.e. when there's no text at
all above that line.
next prev parent reply other threads:[~2023-12-03 16:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E44B7B4B-8FE9-41EB-BF7B-93AC5EAEAC07@gmail.com>
2023-11-29 20:31 ` bug#67533: SVG images confound position pixel measurements JD Smith
2023-11-30 17:32 ` Eli Zaretskii
2023-11-30 21:00 ` JD Smith
2023-12-01 7:08 ` Eli Zaretskii
2023-12-01 22:04 ` JD Smith
2023-12-02 7:30 ` Eli Zaretskii
2023-12-02 13:36 ` JD Smith
2023-12-02 14:18 ` Eli Zaretskii
2023-12-02 19:39 ` Eli Zaretskii
2023-12-02 21:44 ` JD Smith
2023-12-03 3:04 ` JD Smith
2023-12-03 13:02 ` Eli Zaretskii
2023-12-03 15:48 ` JD Smith
2023-12-03 15:52 ` Eli Zaretskii
2023-12-03 16:31 ` Eli Zaretskii
2023-12-03 21:25 ` JD Smith
2023-12-03 23:14 ` JD Smith
2023-12-04 3:27 ` Eli Zaretskii
2023-12-04 4:32 ` JD Smith
2023-12-04 13:11 ` Eli Zaretskii
2023-12-04 14:14 ` JD Smith
2023-12-16 9:32 ` Eli Zaretskii
2023-12-16 15:07 ` JD Smith
2023-12-16 15:23 ` Eli Zaretskii
2023-12-03 15:49 ` JD Smith
2023-12-03 16:33 ` Eli Zaretskii [this message]
2023-12-03 18:58 ` JD Smith
2023-12-01 14:40 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-01 14:55 ` Eli Zaretskii
2023-12-01 15:21 ` JD Smith
2023-12-01 15:36 ` Eli Zaretskii
2023-12-01 15:45 ` JD Smith
2023-12-01 15:59 ` Eli Zaretskii
2023-12-01 16:17 ` JD Smith
2023-12-01 16:30 ` Eli Zaretskii
2023-12-01 16:27 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-01 16:31 ` 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=83fs0j6ybi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67533@debbugs.gnu.org \
--cc=jdtsmith@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).