From: Eli Zaretskii <eliz@gnu.org>
To: Brahimi Saifullah <brahimi.saifullah@gmail.com>
Cc: 51995@debbugs.gnu.org
Subject: bug#51995: 29.0.50; `string-pixel-width' depends on the current window width
Date: Sun, 21 Nov 2021 08:34:34 +0200 [thread overview]
Message-ID: <83ee7arp8l.fsf@gnu.org> (raw)
In-Reply-To: <84h7c67bdi.fsf@gmail.com> (message from Brahimi Saifullah on Sat, 20 Nov 2021 18:42:01 -0300)
> Date: Sat, 20 Nov 2021 18:42:01 -0300
> From: Brahimi Saifullah <brahimi.saifullah@gmail.com>
> Cc: 51995@debbugs.gnu.org
>
> >Since 'window-text-pixel-size' has to deal with arbitrary buffers, it is
> >not a good idea to set X-LIMIT or Y-LIMIT to very large values. The
> >doc-string of 'window-text-pixel-size' explicitly warns about X-LIMIT
> >that
> >
> > Since calculating the width of long lines can take some time, it's
> > always a good idea to make this argument as small as possible; in
> > particular, if the buffer contains long lines that shall be truncated
> > anyway.
>
> I saw the warnings, but I'm unsure of their validity.
> Here are some benchmarks that I did. Each form was run on a fresh emacs -Q.
> Apologies in advance if there is something wrong about them:
>
> ;;; X-LIMIT nil (window width is the limit)
> (benchmark-run 100000
> (save-window-excursion
> (with-temp-buffer
> (set-window-buffer nil (current-buffer))
> (insert "foo")
^^^
He mean a REALLY long line. Like thousands of characters.
next prev parent reply other threads:[~2021-11-21 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 5:04 bug#51995: 29.0.50; `string-pixel-width' depends on the current window width Brahimi Saifullah
2021-11-20 7:20 ` Eli Zaretskii
2021-11-20 8:48 ` martin rudalics
2021-11-20 9:35 ` Lars Ingebrigtsen
2021-11-20 21:36 ` Brahimi Saifullah
2021-11-20 21:42 ` Brahimi Saifullah
2021-11-21 6:34 ` Eli Zaretskii [this message]
2021-11-21 9:12 ` martin rudalics
2021-11-21 18:38 ` Brahimi Saifullah
2021-11-22 9:28 ` martin rudalics
2021-11-22 11:04 ` Lars Ingebrigtsen
2021-11-22 0:53 ` Brahimi Saifullah
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=83ee7arp8l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51995@debbugs.gnu.org \
--cc=brahimi.saifullah@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).