GNU bug report logs - #54131
29.0.50; Flyspell incorrectly reports first word in Python f-string

Previous Next

Package: emacs;

Reported by: Philipp Stephani <p.stephani2 <at> gmail.com>

Date: Wed, 23 Feb 2022 18:17:02 UTC

Severity: normal

Found in version 29.0.50

Full log


Message #32 received at 54131 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Visuwesh <visuweshm <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, p.stephani2 <at> gmail.com, 54131 <at> debbugs.gnu.org
Subject: Re: bug#54131: 29.0.50; Flyspell incorrectly reports first word in
 Python f-string
Date: Thu, 24 Feb 2022 15:36:46 +0100
Visuwesh <visuweshm <at> gmail.com> writes:

> I misspell parts of a symbol quite often so rebinding M-$ to a command
> that NOOPs when the point is not over a comment/string would end up
> annoying, IMO.  I am not sure how common this usecase is though.

I think it's pretty common.  I think a new command that does what
ispell-comment-or-string-at-point does if we're in a comment/string and
what ispell-word does otherwise might be nice.

And flyspell-prog-mode could rebind `M-$', as Eli suggests, but to that
new command.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 3 years and 112 days ago.

Previous Next


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