From: David Kastrup <dak@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Overlay mechanic improvements
Date: Sun, 21 Sep 2014 15:52:27 +0200 [thread overview]
Message-ID: <87y4tdnkro.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1XVhId-0001Hj-0a@fencepost.gnu.org> (Richard Stallman's message of "Sun, 21 Sep 2014 09:35:35 -0400")
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> preview-latex <URL:http://www.gnu.org/software/auctex/preview-latex>
> extensively uses overlays (and they can easily grow to a few thousand
> per document in a mathematically oriented paper),
>
> How many overlays would appear on one screen?
Probably rarely more than a few dozen (that would mostly be the case
when using lots of inline math for small expressions like $a_i$).
> Quadratic behavior for the markers used as start- and end markers is
> clearly undesirable.
>
> The existing code should be fat if you recenter the overlays
> frequently at point, unless you have lots of overlays on one screen.
> Do you recenter them?
Not that I know of.
> If so, why is it slow?
>
> Why aren't text properties right for this?
Because you don't want _anything_ that text properties do. You don't
want to have the stuff cut&paste, you don't want to have the buffer
modified because images are switched on and off, you most definitely
don't want ever to split its identity in two if there are insertions in
the middle, you don't want anything inserted anywhere inheriting
anything from it.
"We did not bother making overlays work efficiently" is not the right
criterion for choosing between overlays and text properties.
--
David Kastrup
next prev parent reply other threads:[~2014-09-21 13:52 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 14:59 Overlay mechanic improvements Vladimir Kazanov
2014-09-19 17:22 ` Stefan Monnier
2014-09-20 13:19 ` Richard Stallman
2014-09-20 13:37 ` David Kastrup
2014-09-21 13:35 ` Richard Stallman
2014-09-21 13:52 ` David Kastrup [this message]
2014-09-21 21:48 ` Richard Stallman
2014-09-21 22:06 ` David Kastrup
2014-09-22 23:11 ` Richard Stallman
2014-09-22 23:50 ` David Kastrup
2014-09-23 19:15 ` Richard Stallman
2014-09-21 16:07 ` Stefan Monnier
2014-09-21 16:14 ` David Kastrup
2014-09-21 21:48 ` Richard Stallman
2014-09-21 22:19 ` David Kastrup
2014-09-23 19:16 ` Richard Stallman
2014-09-23 19:27 ` David Kastrup
2014-09-28 23:24 ` Richard Stallman
2014-09-29 5:45 ` David Kastrup
2014-09-29 20:48 ` Richard Stallman
2014-09-30 1:21 ` Stephen J. Turnbull
2014-09-30 8:43 ` David Kastrup
2014-09-30 10:35 ` Rasmus
2014-09-30 14:22 ` Eli Zaretskii
2014-09-30 16:20 ` David Kastrup
2014-09-30 16:35 ` Eli Zaretskii
2014-09-30 14:32 ` Stefan Monnier
2014-10-02 16:12 ` Uwe Brauer
2014-09-30 19:23 ` Richard Stallman
2014-10-01 3:38 ` Stephen J. Turnbull
2014-10-01 12:53 ` Richard Stallman
2014-10-01 13:11 ` David Kastrup
2014-10-02 1:26 ` Stephen J. Turnbull
2014-09-30 5:52 ` David Kastrup
2014-10-06 19:14 ` Richard Stallman
2014-10-06 21:02 ` David Kastrup
2014-09-21 16:56 ` Eli Zaretskii
2014-09-21 18:42 ` Stefan Monnier
2014-09-21 18:58 ` Eli Zaretskii
2014-09-21 20:12 ` Stefan Monnier
2014-09-21 21:48 ` Richard Stallman
2014-09-22 0:31 ` Stefan Monnier
2014-09-22 23:11 ` Richard Stallman
2014-09-20 15:56 ` Eli Zaretskii
2014-09-20 19:49 ` Stefan Monnier
2014-09-21 13:36 ` Richard Stallman
2014-09-19 18:03 ` Richard Stallman
2014-09-20 8:08 ` Vladimir Kazanov
2014-09-20 13:21 ` Richard Stallman
2014-09-20 16:28 ` Stephen Leake
2014-09-20 13:21 ` Tokenizing Richard Stallman
2014-09-20 16:24 ` Tokenizing Stephen Leake
2014-09-20 16:40 ` Tokenizing Vladimir Kazanov
2014-09-20 20:16 ` Tokenizing Eric Ludlam
2014-09-20 20:35 ` Tokenizing Vladimir Kazanov
2014-09-21 15:13 ` parsing (was tokenizing) Stephen Leake
2014-09-20 16:36 ` Tokenizing Vladimir Kazanov
2014-09-20 19:55 ` Tokenizing Stefan Monnier
2014-09-21 15:35 ` Tokenizing Stephen Leake
2014-09-21 16:43 ` Tokenizing Stefan Monnier
2014-09-22 14:05 ` Tokenizing Stephen Leake
2014-09-21 13:35 ` Tokenizing Richard Stallman
2014-09-21 14:24 ` Tokenizing Vladimir Kazanov
2014-09-21 15:32 ` Tokenizing Stephen Leake
2014-09-21 16:42 ` Tokenizing Stefan Monnier
2014-09-21 18:55 ` Tokenizing Vladimir Kazanov
2014-09-21 22:01 ` Tokenizing Daniel Colascione
2014-09-22 10:21 ` Tokenizing Vladimir Kazanov
2014-09-22 13:55 ` Tokenizing Daniel Colascione
2014-09-22 14:02 ` Tokenizing Stephen Leake
2014-09-22 14:14 ` Tokenizing Daniel Colascione
2014-09-22 13:15 ` Tokenizing Stephen Leake
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=87y4tdnkro.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).