all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 61814@debbugs.gnu.org
Subject: bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell
Date: Sun, 26 Feb 2023 17:11:40 +0200	[thread overview]
Message-ID: <83o7pgihqr.fsf@gnu.org> (raw)
In-Reply-To: <87wn44a327.fsf@gmail.com> (message from Augusto Stoffel on Sun,  26 Feb 2023 15:56:00 +0100)

> 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.

I'm not sure I understand the problem: just don't spell-check the word
at point and don't put any overlays there, and that's all.  Right?
Bonus points for doing this for the word at point only when the last
command was one of a list of known commands, like self-insert-command,
delete-char, yank, etc.





  reply	other threads:[~2023-02-26 15:11 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 [this message]
2023-02-26 15:36   ` Augusto Stoffel
2023-02-26 15:45     ` Eli Zaretskii
2023-02-27  8:31 ` Yuan Fu
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83o7pgihqr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61814@debbugs.gnu.org \
    --cc=arstoffel@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 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.