From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9470@debbugs.gnu.org, larsi@gnus.org
Subject: bug#9470: 24.0.50; Possible bidi-related slowness
Date: Sun, 11 Sep 2011 01:18:17 -0400 [thread overview]
Message-ID: <jwv39g3slu2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1R2c8H-0005HB-Fm@fencepost.gnu.org> (Eli Zaretskii's message of "Sun, 11 Sep 2011 00:59:05 -0400")
> I don't see any easy way of gaining from more aggressive caching of
> this info, because the cache would need to be updated on every edit
> and on any redisplay, which would just move the slowdown from one
> group of commands to another. Clever ideas are welcome.
I'd guess that a cache that stores (START . END) could help, where
"START is a position that starts a paragraph and that paragraph ends no
sooner than END".
This way when working within a very long paragraph, you only need to
look for a paragraph boundary between END and point and if there isn't
any, you can go straight to START without searching for it.
Stefan
next prev parent reply other threads:[~2011-09-11 5:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 18:28 bug#9470: 24.0.50; Possible bidi-related slowness Lars Magne Ingebrigtsen
2011-09-10 18:45 ` Christoph Scholtes
2011-09-10 19:15 ` Eli Zaretskii
2011-09-10 20:28 ` Christoph Scholtes
2011-09-10 19:26 ` Eli Zaretskii
2011-09-10 19:25 ` Lars Magne Ingebrigtsen
2011-09-10 19:41 ` Eli Zaretskii
2011-09-10 19:41 ` Lars Magne Ingebrigtsen
2011-09-10 20:10 ` Eli Zaretskii
2011-09-10 20:11 ` Lars Magne Ingebrigtsen
2011-09-10 20:34 ` Eli Zaretskii
2011-09-10 20:42 ` Lars Magne Ingebrigtsen
2011-09-10 20:53 ` Eli Zaretskii
2011-09-11 3:06 ` Stefan Monnier
2011-09-11 4:59 ` Eli Zaretskii
2011-09-11 5:18 ` Stefan Monnier [this message]
2011-09-11 6:25 ` Eli Zaretskii
2011-09-12 2:49 ` Stefan Monnier
2011-09-12 7:21 ` Eli Zaretskii
2011-09-13 2:21 ` Stefan Monnier
2011-09-17 15:22 ` Eli Zaretskii
2011-09-18 7:33 ` Lars Magne Ingebrigtsen
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=jwv39g3slu2.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9470@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.