From: Yuan Fu <casouri@gmail.com>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: eliz@gnu.org, 61814@debbugs.gnu.org
Subject: bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell
Date: Mon, 27 Feb 2023 00:31:19 -0800 [thread overview]
Message-ID: <EE386875-92C9-4F85-9B67-049BAA7735FB@gmail.com> (raw)
In-Reply-To: <87wn44a327.fsf@gmail.com>
Augusto Stoffel <arstoffel@gmail.com> writes:
> On Sun, 26 Feb 2023 at 17:11, Eli Zaretskii wrote:
>
>>> From: Augusto Stoffel <arstoffel@gmail.com>
>>> Date: Sun, 26 Feb 2023 15:56:00 +0100
>>>
>>> Also, one obvious glitch is that one gets JIT™ corrections for the word
>>> being currently typed. Before going on an writing some ugly logic to
>>> avoid that, and since one can influence an overlay appearance when the
>>> mouse pointer hovers it, I was wondering if there's something analogous
>>> for the cursor.
There is ‘cursor-sensor-functions’, but it requires
‘cursor-sensor-functions’ to be on. IIUC you want the squiggly lines
remain invisible until point leaves the overlay, right? You probably
have thought of this, but what about simply checking whether there is
any whitespace character between point and the word being checked,
before creating the overlay? Would that work?
next prev parent reply other threads:[~2023-02-27 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 14:56 bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell Augusto Stoffel
2023-02-26 15:11 ` Eli Zaretskii
2023-02-26 15:36 ` Augusto Stoffel
2023-02-26 15:45 ` Eli Zaretskii
2023-02-27 8:31 ` Yuan Fu [this message]
2023-02-27 9:58 ` Augusto Stoffel
2023-03-04 11:41 ` Augusto Stoffel
2023-03-04 22:59 ` Yuan Fu
2023-03-06 10:52 ` Augusto Stoffel
2023-03-06 12:15 ` Eli Zaretskii
2023-03-08 0:45 ` Yuan Fu
2023-03-07 18:25 ` Juri Linkov
2023-03-08 8:50 ` Augusto Stoffel
2023-03-08 13:57 ` 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=EE386875-92C9-4F85-9B67-049BAA7735FB@gmail.com \
--to=casouri@gmail.com \
--cc=61814@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.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 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).