From: JD Smith <jdtsmith@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67533@debbugs.gnu.org
Subject: bug#67533: SVG images confound position pixel measurements
Date: Sun, 3 Dec 2023 13:58:26 -0500 [thread overview]
Message-ID: <5DB1A264-C46A-4509-973D-6BE77936D1FE@gmail.com> (raw)
In-Reply-To: <83fs0j6ybi.fsf@gnu.org>
> On Dec 3, 2023, at 11:33 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> 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.
Thanks, all set on this end. Just mentioning the use-case for the casual reader who may wonder what real world impact it has.
next prev parent reply other threads:[~2023-12-03 18:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 19:02 SVG images confound position pixel measurements JD Smith
2023-11-29 20:31 ` bug#67533: " 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
2023-12-03 18:58 ` JD Smith [this message]
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
2023-12-01 8:36 ` Manuel Giraud via Emacs development discussions.
2023-12-01 14:11 ` JD Smith
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5DB1A264-C46A-4509-973D-6BE77936D1FE@gmail.com \
--to=jdtsmith@gmail.com \
--cc=67533@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.