From: Dmitry Gutov <dgutov@yandex.ru>
To: "Eli Zaretskii" <eliz@gnu.org>, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 30462@debbugs.gnu.org
Subject: bug#30462: flyspell-auto-correct-word 'corrects' more than the current word
Date: Fri, 16 Feb 2018 12:15:52 +0200 [thread overview]
Message-ID: <6d3dc737-73ae-e6c6-5058-85d73421f9e9@yandex.ru> (raw)
In-Reply-To: <838tbuw5st.fsf@gnu.org>
On 2/15/18 7:56 PM, Eli Zaretskii wrote:
>> I would respectfully say fix it to act like its documentation.
>
> That would change its long-standing behavior in incompatible ways, so
> I don't think we can do that.
I respectfully disagree. The current behavior is both undocumented and
dangerous.
>> And make reaching into the dark corners of your document that you are
>> not aware of and changing words ... into a non-default bonus feature...
>> or move it into M-x dissociated-press.
>
> I'm okay with making this behavior optional, but it will have to be on
> by default, for backward compatibility.
Is it really that important in this case? We're allowed to change the
defaults from time to time.
And having C-M-i (bound to completion-at-point in most other contexts)
do something like this is a bad UI.
next prev parent reply other threads:[~2018-02-16 10:15 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d3dc737-73ae-e6c6-5058-85d73421f9e9@yandex.ru \
--to=dgutov@yandex.ru \
--cc=30462@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).