GNU bug report logs - #32142
WG: 26.1; Problems with flyspell-region

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#32142: closed (WG: 26.1; Problems with flyspell-region)
Date: Sat, 14 Jul 2018 15:57:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 14 Jul 2018 18:56:05 +0300
with message-id <83zhytak16.fsf <at> gnu.org>
and subject line Re: bug#32142: WG: 26.1; Problems with flyspell-region
has caused the debbugs.gnu.org bug report #32142,
regarding WG: 26.1; Problems with flyspell-region
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
32142: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32142
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: "R. Diez" <rdiezmail-emacs <at> yahoo.de>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: WG: 26.1; Problems with flyspell-region
Date: Fri, 13 Jul 2018 15:11:13 +0000 (UTC)

I mentioned some problems with flyspell-region on the help-gnu-emacs mailing list here:

https://lists.gnu.org/archive/html/help-gnu-emacs/2018-07/msg00100.html
Issues are:


Issue 1) The spell check is performed just once, and is not updated as I type inside that region. This is what I wrote on the mailing list:


"If I mark a region (click on the beginning, hold shift, move to the end), and then run flyspell-region, the region gets spell-checked, and all the dictionary misses are underlined in red, as expected. But then, if I fix the words, the spelling marking (the red underlining) is not removed. It looks like Flyspell is not 'live' anymore within that region. The "overlay" is left behind as static font faces."
I do not want to activate Flyspell for the whole buffer, because that would lead to too much red underlining.

If I just wanted a single-shot, I would use ispell-region instead.

If this cannot be fixed, the current behaviour should be documented.



Issue 2) There is no easy way to remove the red underlining (overlays) left behind by flyspell-region. This is what I wrote on the mailing list:

"Often I get too many dictionary misses (too much red underlining). Or I just do not want to be distracted anymore. That is the reason why I want to be able to turn spell-checking on and off on demand on a particular region. And, when I want it off, I want to remove the "overlays" from that region. Why should they remain? At the moment, there is no direct way to do that."

I also wrote:

"After some searching, I found out about flyspell-delete-all-overlays and flyspell-delete-region-overlays, but alas, they are not marked as 'interactive'. I wonder how Flyspell thinks users should remove those marks (how to end the flyspell-region command)."

Issue 3) Disabling flyspell-persistent-highlight renders flyspell-region useless.

Contrary to some of the answers in the mailing list, that combination does not work at all. This is what I am seeing:

"What I mean is that, if you turn flyspell-persistent-highlight off, then flyspell-region does nothing other than consume CPU cycles. The red underlining for dictionary misses does not show up at all."

Again, I do not want to turn on Flyspell for the whole buffer. If flyspell-region is supposed to work only when the Flyspell Mode is active, it should check, and error if it is not active. But that kind of defeats the purpose of having a flyspell-region.

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: "R. Diez" <rdiezmail-emacs <at> yahoo.de>
Cc: 32142-done <at> debbugs.gnu.org
Subject: Re: bug#32142: WG: 26.1; Problems with flyspell-region
Date: Sat, 14 Jul 2018 18:56:05 +0300

> From: "R. Diez" <rdiezmail-emacs <at> yahoo.de>
> Cc: 32142 <at> debbugs.gnu.org
> Date: Sat, 14 Jul 2018 17:15:12 +0200
> 
> - I cannot type 'C-u M-$' to resume spell-checking, because Ctrl+U is 
> mapped to something else on my config, and I cannot get M-$ to work 
> anyway with my German keyboard. Or maybe because Alt+4 ('$' is on the 
> '4' key) is mapped to something else. Who knows.

I fixed this blunder, and I'm marking the bug done.

Thanks for your report and suggestions.

Previous Next

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