unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ynyaaa@gmail.com
Cc: 26051@debbugs.gnu.org
Subject: bug#26051: 25.1; overlays may make emacs very slow
Date: Sun, 12 Mar 2017 17:47:47 +0200	[thread overview]
Message-ID: <83fuiicx98.fsf@gnu.org> (raw)
In-Reply-To: <871su3nua2.fsf@gmail.com> (ynyaaa@gmail.com)

> From: ynyaaa@gmail.com
> Cc: 26051@debbugs.gnu.org
> Date: Sun, 12 Mar 2017 10:44:21 +0900
> 
> >>   "@%d\n"
> >>   "?%d\n"
> >>   "\u00E1%d\n" ;; LATIN SMALL LETTER A WITH ACUTE
> >>   "\u3042%d\n" ;; HIRAGANA LETTER A
> >>   "\u4E00%d\n" ;; CJK IDEOGRAPH-4E00
> >>   "\uFF41%d\n" ;; FULLWIDTH LATIN SMALL LETTER A
> >
> > What I see here, with all of the above except the first two, is that
> > what takes a long time is for the code to run; once I see "Done" in
> > the echo area, redisplay takes less than a second.
> 
> Why is it take long time to use multibyte characters?
> 2 seconds and 2 minutes are very different.

My guess is because we need to compute the byte position of the
markers that store the overlay's beginning and end.  But that's just a
guess.

Btw, your original recipe will produce a much faster redisplay if you
set bidi-paragraph-direction of the buffer to left-to-right, instead
of leaving it at its default nil value.  Sorry I didn't mention this
earlier.





  reply	other threads:[~2017-03-12 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 16:25 bug#26051: 25.1; overlays may make emacs very slow ynyaaa
2017-03-10 17:02 ` Eli Zaretskii
2017-03-11  4:22 ` ynyaaa
2017-03-11  6:59   ` Eli Zaretskii
2017-03-12  1:44     ` ynyaaa
2017-03-12 15:47       ` Eli Zaretskii [this message]
2017-03-13 11:18         ` ynyaaa
2017-03-13 11:29           ` Andreas Politz
2017-03-13 15:54             ` Eli Zaretskii

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=83fuiicx98.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26051@debbugs.gnu.org \
    --cc=ynyaaa@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).