[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell
From: |
Eli Zaretskii |
Subject: |
bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell |
Date: |
Mon, 06 Mar 2023 14:15:32 +0200 |
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, eliz@gnu.org,
> 61814@debbugs.gnu.org
> Date: Mon, 06 Mar 2023 11:52:53 +0100
>
> On Sat, 4 Mar 2023 at 14:59, Yuan Fu wrote:
>
> > wucuo.el also caused an issue when I opened a buffer with some inline
> > images. The inline image is the raw image data encoded in base64
> > inserted into the file as a string, plus a display text property over
> > the whole string displaying it as the image. wucuo.el thinks that huge
> > string is visible in the window (because of the display text
> > property), and tries to spell check that huge string, and got stuck.
>
> wucuo.el seems to be synchronous like Flyspell, so that sounds like a
> big problem.
>
> Anyway, which major mode does that? AFAIK the usual is to have the
> underlying text of an image just a space or something similar.
Just visit any image file with "C-x C-f", and you will see this in
action.