From: Eli Zaretskii <eliz@gnu.org>
To: 30462@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#30462: flyspell-auto-correct-word 'corrects' more than the current word
Date: Thu, 15 Feb 2018 14:00:59 +0200 [thread overview]
Message-ID: <A5387B5E-669D-45CE-893F-C3C0C8760711@gnu.org> (raw)
In-Reply-To: <87h8qi93dy.fsf@jidanni.org>
On February 15, 2018 8:24:25 AM GMT+02:00, "積丹尼 Dan Jacobson" <jidanni@jidanni.org> wrote:
> C-M-i (translated from <escape> <tab>) runs the command
> flyspell-auto-correct-word (found in flyspell-mode-map), which is an
> interactive compiled Lisp function in ‘flyspell.el’.
>
> It is bound to C-., C-M-i.
>
> (flyspell-auto-correct-word)
>
> Correct the current word.
> This command proposes various successive corrections for the current
> word.
>
> Well it turns out if the current word is already correct, then it
> searches backward up to several sentences looking for another word
> that
> it can correct.
>
> Which can have disastrous consequences when the boss reads the final
> draft of what you sent him.
>
> Therefore it would be best if this command would limit its helpfulness
> to what it says in the docstring: the current word.
>
> Which to me means not some word 30 words back.
This happens only if you invoke the command more than once on the same
location. So, while I agree that the doc string should be fixed, the problem
you describe can happen only by user request.
next prev parent reply other threads:[~2018-02-15 12:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 6:24 bug#30462: flyspell-auto-correct-word 'corrects' more than the current word 積丹尼 Dan Jacobson
2018-02-15 12:00 ` Eli Zaretskii [this message]
2018-02-15 12:56 ` 積丹尼 Dan Jacobson
2018-02-15 16:56 ` Eli Zaretskii
2018-02-16 0:22 ` 積丹尼 Dan Jacobson
2018-02-16 10:15 ` Dmitry Gutov
2018-02-16 10:55 ` Eli Zaretskii
2018-02-16 11:03 ` 積丹尼 Dan Jacobson
2018-02-16 11:36 ` Dmitry Gutov
2018-02-16 13:47 ` Eli Zaretskii
2018-02-16 14:18 ` Eli Zaretskii
2018-02-16 14:33 ` Eli Zaretskii
2018-02-17 0:58 ` 積丹尼 Dan Jacobson
2018-02-17 7:47 ` Eli Zaretskii
2018-02-17 11:43 ` 積丹尼 Dan Jacobson
2018-02-17 14:51 ` 積丹尼 Dan Jacobson
2018-02-17 15:13 ` 積丹尼 Dan Jacobson
2018-02-17 16:09 ` Eli Zaretskii
2018-02-17 23:37 ` 積丹尼 Dan Jacobson
2018-02-20 0:24 ` Dmitry Gutov
2018-02-20 4:08 ` Eli Zaretskii
2018-03-03 10:49 ` Eli Zaretskii
2018-02-20 0:28 ` Dmitry Gutov
2018-02-20 4:24 ` Eli Zaretskii
2018-02-20 11:38 ` Dmitry Gutov
2018-02-20 17:57 ` 積丹尼 Dan Jacobson
2018-02-20 0:51 ` Dmitry Gutov
2018-02-18 0:14 ` Richard Stallman
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=A5387B5E-669D-45CE-893F-C3C0C8760711@gnu.org \
--to=eliz@gnu.org \
--cc=30462@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/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.