unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: vincent.belaiche@gmail.com (Vincent Belaïche)
Cc: 22519@debbugs.gnu.org, vincent.belaiche@gmail.com
Subject: bug#22519: 25.1.50; Emacs gets stuck while doing incremental search forward
Date: Wed, 16 Mar 2016 22:24:31 +0200	[thread overview]
Message-ID: <83k2l29nnk.fsf@gnu.org> (raw)
In-Reply-To: <84lh5i9v8n.fsf@gmail.com> (vincent.belaiche@gmail.com)

> From: vincent.belaiche@gmail.com (Vincent Belaïche)
> Cc: Vincent Belaïche <vincent.belaiche@gmail.com>,
>   22519@debbugs.gnu.org
> Date: Wed, 16 Mar 2016 18:40:40 +0100
> 
> > If you are talking about the fact that Emacs searches for a character
> > in any fonts it thinks might be able to display it, then this isn't a
> > bug.  What else could Emacs do, when presented with a character that
> > cannot be displayed with fonts that are already loaded?
> 
> I don't this that _this_ as such is a bug, what is more annoying is that
> the slow-down lasts longer than the first scroll into the area where
> these characters are.

If the character wasn't found, then it makes sense to try looking up
the fonts again -- the user could install new fonts since the last
time.

> I could stay on the same region for hours, and whenever I made an
> edit it was slow --- loosing the WYSIWYGiness of the edition, that
> is I was seeing the full result of what I had typed one or two
> seconds after the typing had started.

Every redisplay might trigger another search for a suitable font.  The
solution really is to install the fonts you need.

Can we now close this bug?





  reply	other threads:[~2016-03-16 20:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84vb4rhag0.fsf@gmail.com>
2016-03-12 17:46 ` bug#22519: 25.1.50; Emacs gets stuck while doing incremental search forward Eli Zaretskii
2016-03-13  7:11   ` Vincent Belaïche
2016-03-13  8:10     ` Vincent Belaïche
2016-03-13 16:19       ` Eli Zaretskii
2016-03-15 13:28         ` Vincent Belaïche
2016-03-15 15:53           ` Vincent Belaïche
2016-03-15 18:11           ` Eli Zaretskii
2016-03-16 11:16             ` Vincent Belaïche
2016-03-16 16:08               ` Eli Zaretskii
2016-03-16 17:40                 ` Vincent Belaïche
2016-03-16 20:24                   ` Eli Zaretskii [this message]
2016-03-17  9:14                     ` Vincent Belaïche
2016-03-17 16:20                       ` Eli Zaretskii
2016-05-24 10:16                         ` Vincent Belaïche
2016-05-24 15:31                           ` Eli Zaretskii
2016-12-07 19:41                             ` Glenn Morris
2016-02-01  9:04 Vincent Belaïche
2016-02-01 19:06 ` Eli Zaretskii
2016-02-02  7:18 ` Vincent Belaïche
2016-02-02 16:16   ` Eli Zaretskii
2016-03-10 12:18     ` Vincent Belaïche

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=83k2l29nnk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22519@debbugs.gnu.org \
    --cc=vincent.belaiche@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).