From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: psainty@orcon.net.nz, rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: 27.0.50: How can I test a buffer-local window-configuration-change-hook in batch mode?
Date: Sat, 26 Oct 2019 11:59:16 -0400 [thread overview]
Message-ID: <jwvftjfcxsu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <837e4rvg9s.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Oct 2019 15:32:31 +0300")
>> >> I don't think long lines pose any performance problems in buffers
>> >> which are never displayed
>> > You are wrong: it will cause problems in any function that uses the
>> > display code, even if nothing is displayed. For example,
>> > vertical-motion, next-line, posn-at-point, etc. all use the display
>> > code internally.
>> In theory you're right. But I think in practice "buffers that aren't
>> displayed" is a pretty good approximation of "so-long won't help".
> I don't understand how practice makes theory unimportant in this case.
> There's a leap in your logic that I couldn't follow.
The `so-long` package is a trade-off: it has advantages (supposedly
avoids some nasty slowdowns) and disadvantages (it works by disabling
some features).
It's virtually impossible to determine reliably when it's better to use
so-long and when it's better not to. So theory is not super relevant
compared to actual practical experience.
I don't have an opinion on whether so-long should (by default) only be
enabled in buffers that are displayed, but it intuitively sound like
a potentially good heuristic to minimize the risk of breaking stuff.
>> I missed something: which new hook would be needed?
> This sub-thread was in response to Martin's question here:
> https://lists.gnu.org/archive/html/emacs-devel/2019-10/msg01013.html
Ah, I see. I thought (and still think) it was just a misunderstanding
on Martin's part, not an actual need (at least Phil didn't express
a need for it).
[ Or maybe this particular case just reminded Martin of other cases
where such a hook could have been handy. ]
Stefan
next prev parent reply other threads:[~2019-10-26 15:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 10:50 27.0.50: How can I test a buffer-local window-configuration-change-hook in batch mode? Phil Sainty
2019-10-24 14:23 ` Eli Zaretskii
2019-10-24 23:53 ` Phil Sainty
2019-10-25 8:37 ` Eli Zaretskii
2019-10-25 9:20 ` martin rudalics
2019-10-25 9:34 ` Eli Zaretskii
2019-10-26 7:49 ` martin rudalics
2019-10-26 9:08 ` Eli Zaretskii
2019-10-25 10:31 ` Phil Sainty
2019-10-25 12:42 ` Eli Zaretskii
2019-10-25 12:53 ` Stefan Monnier
2019-10-25 13:57 ` Eli Zaretskii
2019-10-25 15:27 ` Stefan Monnier
2019-10-25 18:41 ` Eli Zaretskii
2019-10-26 12:33 ` Lars Ingebrigtsen
2019-10-26 12:53 ` Eli Zaretskii
2019-10-26 13:13 ` Lars Ingebrigtsen
2019-10-26 13:33 ` Eli Zaretskii
2019-10-26 13:50 ` Lars Ingebrigtsen
2019-10-26 14:34 ` Eli Zaretskii
2019-10-26 14:45 ` Lars Ingebrigtsen
2019-10-26 15:07 ` Eli Zaretskii
2019-10-25 13:16 ` Phil Sainty
2019-10-25 13:44 ` Eli Zaretskii
2019-10-25 8:51 ` martin rudalics
2019-10-25 10:54 ` Phil Sainty
2019-10-26 7:49 ` martin rudalics
2019-10-26 9:07 ` Eli Zaretskii
2019-10-26 10:57 ` Phil Sainty
2019-10-26 11:28 ` Eli Zaretskii
2019-10-26 12:11 ` Stefan Monnier
2019-10-26 12:32 ` Eli Zaretskii
2019-10-26 15:59 ` Stefan Monnier [this message]
2019-10-26 16:28 ` Eli Zaretskii
2019-10-26 17:14 ` Stefan Monnier
2019-10-26 17:35 ` Eli Zaretskii
2019-10-26 19:53 ` Stefan Monnier
2019-10-26 20:18 ` Eli Zaretskii
2019-10-26 13:09 ` Phil Sainty
2019-10-26 13:31 ` Eli Zaretskii
2019-10-26 12:05 ` Stefan Monnier
2019-10-27 7:49 ` martin rudalics
2019-10-27 17:40 ` Stefan Monnier
2019-10-28 9:39 ` martin rudalics
2019-11-10 3:50 ` so-long.el updates (was Re: 27.0.50: How can I test a buffer-local window-configuration-change-hook in batch mode?) Phil Sainty
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=jwvftjfcxsu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=psainty@orcon.net.nz \
--cc=rudalics@gmx.at \
/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).