From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#32142: WG: 26.1; Problems with flyspell-region Date: Sat, 14 Jul 2018 10:45:39 +0300 Message-ID: <83lgaeb6qk.fsf@gnu.org> References: <745366070.6138533.1531494673065.ref@mail.yahoo.com> <745366070.6138533.1531494673065@mail.yahoo.com> <83zhyuc45n.fsf@gnu.org> <1411313637.6317903.1531513379661@mail.yahoo.com> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1531554249 2419 195.159.176.226 (14 Jul 2018 07:44:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Jul 2018 07:44:09 +0000 (UTC) Cc: 32142@debbugs.gnu.org To: "R. Diez" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jul 14 09:44:05 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1feFDo-0000WU-Jb for geb-bug-gnu-emacs@m.gmane.org; Sat, 14 Jul 2018 09:44:04 +0200 Original-Received: from localhost ([::1]:40453 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1feFFt-0002DD-U2 for geb-bug-gnu-emacs@m.gmane.org; Sat, 14 Jul 2018 03:46:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49055) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1feFFl-0002D3-1h for bug-gnu-emacs@gnu.org; Sat, 14 Jul 2018 03:46:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1feFFh-0001zL-VE for bug-gnu-emacs@gnu.org; Sat, 14 Jul 2018 03:46:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:51572) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1feFFh-0001zC-QY for bug-gnu-emacs@gnu.org; Sat, 14 Jul 2018 03:46:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1feFFh-0005Et-J2 for bug-gnu-emacs@gnu.org; Sat, 14 Jul 2018 03:46:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 14 Jul 2018 07:46:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32142 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32142-submit@debbugs.gnu.org id=B32142.153155434720116 (code B ref 32142); Sat, 14 Jul 2018 07:46:01 +0000 Original-Received: (at 32142) by debbugs.gnu.org; 14 Jul 2018 07:45:47 +0000 Original-Received: from localhost ([127.0.0.1]:59469 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1feFFS-0005EN-W1 for submit@debbugs.gnu.org; Sat, 14 Jul 2018 03:45:47 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:57999) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1feFFR-0005E9-3j for 32142@debbugs.gnu.org; Sat, 14 Jul 2018 03:45:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1feFFI-0001jK-De for 32142@debbugs.gnu.org; Sat, 14 Jul 2018 03:45:39 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39798) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1feFFI-0001jE-8p; Sat, 14 Jul 2018 03:45:36 -0400 Original-Received: from [176.228.60.248] (port=4633 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1feFFH-0002DT-Lf; Sat, 14 Jul 2018 03:45:36 -0400 In-reply-to: <1411313637.6317903.1531513379661@mail.yahoo.com> (rdiezmail-emacs@yahoo.de) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:148515 Archived-At: > Date: Fri, 13 Jul 2018 20:22:59 +0000 (UTC) > From: "R. Diez" > Cc: "32142@debbugs.gnu.org" <32142@debbugs.gnu.org> > > > That description is inaccurate. The misspelled words _are_ > > highlighted, but then the highlight is removed when > > cursor moves to the next word, per the intended effect of > > flyspell-persistent-highlight being nil. > Once more, that is only the case if flyspell-mode is on. If flyspell-mode is off, and flyspell-persistent-highlight is also off, CPU usage goes up for a short time, and nothing gets marked. That is weird. I think the difference in what we see is related to the size of the region. See the variable 'flyspell-large-region'. > > We don't have a spell-checking feature that watches correction of > > misspelled words without turning on flyspell-mode. > > OK, I gather from your comments that flyspell-region is designed to work with flyspell-mode turned on. And that you are unable or unwilling to change that. That limitation is not obvious. In fact, I would argue that users would expect exactly the opposite from flyspell-region. > > > I request that flyspell-region documents this fact, and/or checks whether flyspell-mode is off and/or flyspell-persistent-highlight is off. I added the caveats to the doc strings of the relevant functions and variables. I object to the "unable or unwilling" part of your complaint. I was just stating the fact that the feature you expected was missing from Emacs, because no one designed and coded it. There's no need to hint on my (non-existent) personal motives and abilities in this matter. This is a volunteer project, and thus will alone is not enough to make things happen. I did my share of minor changes and fixes in flyspell.el, but I'm by no means the only one who is responsible for what happens there. > That would make it clear where the limitations of Flyspell are, and avoid wasting time when it does not work as one probably expects. Because, as I mentioned, > flyspell-region actually makes little sense if you need to have flyspell-mode turned on. FWIW, it makes a lot of sense to me: Flyspell mode is a coherent set of features that are supposed to be used as a whole. I am actually quite surprised that someone could expect flyspell-region to work outside of the mode. Anyway, this is now stated explicitly in the doc string. > ispell-region seems to be no good substitute for what flyspell-region should actually do. After running ispell-region, you cannot move the cursor freely around and comfortably correct words. It is very awkward to use. ??? Did you read the help provided by ispell-region? You could either: . type 'X' to exit spell-check temporarily, correct the word at point, then type 'C-u M-$' to resume spell-checking (the latter command is shown in the echo area when you type 'X'); or . enter recursive-edit with 'C-r', edit the text as you wish, then exit recursive-edit with 'C-M-c' (again, the echo area shows the command to exit when you type 'C-r') and continue spell-checking; or . type 'r' which will allow you to replace the misspelled word with the text you type in the minibuffer; or . type 'R', which works like 'r', but also lets you replace all the other words in the buffer like the one replaced here. These commands (and others) are listed if you type '?' and in more detail by 'C-h f ispell-help', which is mentioned in the text shown by '?'. IME, ispell-region is a very convenient feature for spell-checking large regions of text, much more convenient than flyspell-region. YMMV, of course.