all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 9470@debbugs.gnu.org, larsi@gnus.org
Subject: bug#9470: 24.0.50; Possible bidi-related slowness
Date: Sun, 11 Sep 2011 02:25:59 -0400	[thread overview]
Message-ID: <E1R2dUN-0000xk-La@fencepost.gnu.org> (raw)
In-Reply-To: <jwv39g3slu2.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 11 Sep 2011 01:18:17 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: larsi@gnus.org,  9470@debbugs.gnu.org
> Date: Sun, 11 Sep 2011 01:18:17 -0400
> 
> 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.

I'm not sure I'm following.  Are you assuming that redisplay is
entered immediately after each deletion or insertion, and therefore
these edits are always at point?  Because that assumption is false,
AFAIK: Emacs could perform any number of edits before reentering
redisplay, so changes could be at places that are not at point and not
even in the visible portion of the buffer.  Any of these edits could
insert or delete a paragraph boundary, and thus potentially change the
paragraph direction.

If you don't assume changes at point, then I don't see how point is
relevant to this issue.  Am I missing something?

There are other complications with your proposal, e.g. the need to
look for and keep track of paragraph end, which I currently don't care
about, and the need to recompute the values of START and END when
point moves far way.  But the above is the major one.





  reply	other threads:[~2011-09-11  6:25 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
2011-09-11  6:25                         ` Eli Zaretskii [this message]
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=E1R2dUN-0000xk-La@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=9470@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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.