From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#30462: flyspell-auto-correct-word 'corrects' more than the current word Date: Tue, 20 Feb 2018 02:51:17 +0200 Message-ID: References: <87h8qi93dy.fsf@jidanni.org> <87y3juo1hq.fsf_-_@jidanni.org> <838tbuw5st.fsf@gnu.org> <6d3dc737-73ae-e6c6-5058-85d73421f9e9@yandex.ru> <838tbtdx0p.fsf@gnu.org> <9cee145f-0663-3043-b9b0-5133da1f0b00@yandex.ru> <83606xdp1m.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1519087896 28158 195.159.176.226 (20 Feb 2018 00:51:36 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 20 Feb 2018 00:51:36 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Thunderbird/59.0 Cc: 30462@debbugs.gnu.org, jidanni@jidanni.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Feb 20 01:51:32 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 1enw9N-00061K-7r for geb-bug-gnu-emacs@m.gmane.org; Tue, 20 Feb 2018 01:51:17 +0100 Original-Received: from localhost ([::1]:52993 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1enwBP-0007sr-Hm for geb-bug-gnu-emacs@m.gmane.org; Mon, 19 Feb 2018 19:53:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49590) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1enwAA-0007Jk-SN for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2018 19:52:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1enwA6-0001xY-SR for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2018 19:52:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43987) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1enwA6-0001xQ-O3 for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2018 19:52:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1enwA6-0003HR-9h for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2018 19:52:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 20 Feb 2018 00:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30462 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30462-submit@debbugs.gnu.org id=B30462.151908788812565 (code B ref 30462); Tue, 20 Feb 2018 00:52:02 +0000 Original-Received: (at 30462) by debbugs.gnu.org; 20 Feb 2018 00:51:28 +0000 Original-Received: from localhost ([127.0.0.1]:51884 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1enw9Y-0003Gb-FE for submit@debbugs.gnu.org; Mon, 19 Feb 2018 19:51:28 -0500 Original-Received: from mail-wr0-f172.google.com ([209.85.128.172]:35129) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1enw9W-0003GK-IF for 30462@debbugs.gnu.org; Mon, 19 Feb 2018 19:51:26 -0500 Original-Received: by mail-wr0-f172.google.com with SMTP id l43so11421756wrc.2 for <30462@debbugs.gnu.org>; Mon, 19 Feb 2018 16:51:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=9iCfbpoKNcn+F/m1NwUyv4C1waGWQQI66rytubiQ4WQ=; b=k0Yv4t9RVWQo7PmkUXPXPWHhaz6T7epoW0wvA/YzDAgPkCGlFT5k007X918th4BA66 aehzrDcAsjGDKPfkhwkSbemwCDCAOzcaxDujPSrNF8uJIMGXmxPvBdNwMGuOhW4deOe2 BaIGrs+wZKbSbPrvQiHTxSqFfVKmi8BZNjeQ1TFCzcaLnV8+bwjanuf3NlJ2UsuPl6UX ahayco4njPRuJzoQzLD3CC9r4mPz554Gb8AfSQVzt6KL2QeYkv8c9LnP1cBdYFPugIqq it/AzT/Wduhy4CxEgYcmVEnOF3GgOz4RZHXUr5R6ydT3ozA21NVugTlaMjx2+6NXX8ri HZaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9iCfbpoKNcn+F/m1NwUyv4C1waGWQQI66rytubiQ4WQ=; b=e4+RMqa+213udccPbV01NLNJA8mdDFhPyc3QQZpcjKHgypysJ1RJHRz1tqED3JfmZb dahR3odohy0annvW+c9Cyyp+O5SCbZG4yIVsi+H4C2sRAdwYEt+iBTlalrcI97d+BYVc cJ9RVMRHOWjnp87gBUDNh8nTSBApKwdU/Bar9l96CJ0tK0JPtkfFr7LEhkcIB6FygUqL Zf/GBhCVmyBgHZ+OyZ0OAdi/YAUvKT4mRKhe/BVHYeg6Di+92LzajFp6gOxcW43SYH8h 5SqiukC2MgrZe9mY6mX+F6rnPAafPvJgv/vb4vd7fUFTi2RpZXGOMtERUYWQtjuUPV2N Yalg== X-Gm-Message-State: APf1xPA0/yOCvlrOHCyM4OvyruZ7qTzqKSt8hVwVQfuh4Q0BE+umhrqy i4lFS6b15Pn2Lt+a3NUmY5s= X-Google-Smtp-Source: AH8x227ca04qD6dotNaeCWTkdYmZnh78utLRAD6/SkYtEXO7V9DQtogA/7jfAMg5adTIp/IKy9kr1A== X-Received: by 10.223.183.43 with SMTP id l43mr15419312wre.265.1519087880893; Mon, 19 Feb 2018 16:51:20 -0800 (PST) Original-Received: from [192.168.1.3] ([185.105.174.193]) by smtp.googlemail.com with ESMTPSA id z73sm21361705wmc.3.2018.02.19.16.51.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Feb 2018 16:51:19 -0800 (PST) In-Reply-To: <83606xdp1m.fsf@gnu.org> Content-Language: en-US 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:144030 On 2/16/18 3:47 PM, Eli Zaretskii wrote: > I'm not against a fix, I'm just saying that the fix should not change > the default behavior in totally incompatible ways. That was never the intention, I think. >> It's not like an API stability argument, no third-party Lisp code will >> break after this change. > > I don't see why breaking someone's code is deemed more serious than > breaking someone muscle memory and habits of using Emacs for many > years (this code is in Emacs since July 2000!). To me, they are > equally bad. Someone's code might be used by a lot of users, whereas the muscle memory generally belongs only to one person. In certain situations, code can be harder to fix as well (or, at least, to make sure the fixed version reaches all its users). And indeed, I think our policy has generally been that we can change a default key binding in the next release, but API-breaking Lisp changes have to go through periods of deprecation. > We have no way of knowing that, and in any case having someone come up > in the future with a legitimate question of why did we change this > behavior "just like that" is not a prospect I like, unless e have a > very good answer. Which in this case we don't, not IMO. "Danger of information loss" was a good reason, I believe. Anyway, I think we all agree it's a bug by now. >> If stability to such high degree is the goal, Emacs will more likely >> fade away together with the current generations of its users. > > That's unfair, and also a kind of strawman. Emacs evolves by adding > new features, much more than by changing the existing ones. New > features don't have the "past performance" baggage, so we are free to > design and implement them as we see fit. We can also change existing > features, as long as the deviant behavior, when first introduced, is > opt-in and doesn't change the long-standing defaults. When new and old can coexist, and the old is reasonably serviceable, sure. > Why would someone insist on changing > the default for _everyone_ if they can have it customizable for > themselves to their liking? To answer this question in general: worry about new users (or just unaware ones) and Emacs's reputation.