GNU bug report logs - #30813
26.0.91; flyspell does not recheck after transpose-chars

Previous Next

Package: emacs;

Reported by: Aaron Jensen <aaronjensen <at> gmail.com>

Date: Wed, 14 Mar 2018 00:02:01 UTC

Severity: minor

Found in version 26.0.91

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Aaron Jensen <aaronjensen <at> gmail.com>
Cc: 30813 <at> debbugs.gnu.org
Subject: bug#30813: 26.0.91; flyspell does not recheck after transpose-chars
Date: Wed, 14 Mar 2018 07:28:43 +0200
On March 14, 2018 7:17:14 AM GMT+02:00, Aaron Jensen <aaronjensen <at> gmail.com> wrote:
> On Tue, Mar 13, 2018 at 9:56 PM, Aaron Jensen <aaronjensen <at> gmail.com>
> wrote:
> > Upon some inspection, it seems flyspell is meant to be set up to do
> > this already. See `flyspell-check-pre-word-p', which returns nil in
> > this scenario. Perhaps it can be expanded to handle this scenario.
> 
> For posterity, this works:
> 
>   (defun aj/flyspell-transpose-check ()
>     (with-local-quit
>       (when (and (eq this-command 'transpose-chars)
>                  flyspell-pre-point)
>         (save-excursion
>           (goto-char (- flyspell-pre-point 1))
>           (flyspell-word)))))
> 
> (advice-add 'flyspell-post-command-hook :before
> #'aj/flyspell-transpose-check)
> 
> I'd be happy to include offer a patch for something like this, but I'm
> not sure if there's a better way and/or if it's nasty to hard-code a
> command like this.

 What does that do when C-t is invoked with a numeric argument?

More generally, I think if we want to support transpose commands in flyspell,
we need special code for that, because those commands change two words,
which both need to be checked, something that  flyspell-check-pre-word-p is not
designed to handle.




This bug report was last modified 7 years and 185 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.