From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.bugs Subject: bug#51766: 29.0.50; Return value of buffer-chars-modified-tick changes when buffer text is not yet changed before inserting a character for non-latin input methods Date: Tue, 21 Jun 2022 12:14:54 +0800 Message-ID: <87zgi6r6td.fsf@localhost> References: <87mtmalrs1.fsf@localhost> <837dde200c.fsf@gnu.org> <87k0helmig.fsf@localhost> <831r3m1tpk.fsf@gnu.org> <8735o1r31q.fsf@localhost> <834k8hzi10.fsf@gnu.org> <87zgq9pmb6.fsf@localhost> <831r3lzfk4.fsf@gnu.org> <87wnldpk5x.fsf@localhost> <83zgq9xv1y.fsf@gnu.org> <87r1bkpgjw.fsf@localhost> <87y1xv7ggf.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3277"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 51766@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 21 06:14:09 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o3VHE-0000eZ-Vu for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 21 Jun 2022 06:14:08 +0200 Original-Received: from localhost ([::1]:45700 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o3VHD-00073D-W2 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 21 Jun 2022 00:14:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36656) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o3VH8-000733-4N for bug-gnu-emacs@gnu.org; Tue, 21 Jun 2022 00:14:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36781) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o3VH7-0007vq-Q2 for bug-gnu-emacs@gnu.org; Tue, 21 Jun 2022 00:14:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o3VH7-0004fj-Ii for bug-gnu-emacs@gnu.org; Tue, 21 Jun 2022 00:14:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 21 Jun 2022 04:14:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51766 X-GNU-PR-Package: emacs Original-Received: via spool by 51766-submit@debbugs.gnu.org id=B51766.165578483117934 (code B ref 51766); Tue, 21 Jun 2022 04:14:01 +0000 Original-Received: (at 51766) by debbugs.gnu.org; 21 Jun 2022 04:13:51 +0000 Original-Received: from localhost ([127.0.0.1]:58911 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o3VGw-0004fC-VP for submit@debbugs.gnu.org; Tue, 21 Jun 2022 00:13:51 -0400 Original-Received: from mail-ot1-f50.google.com ([209.85.210.50]:40647) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o3VGu-0004ey-Gj for 51766@debbugs.gnu.org; Tue, 21 Jun 2022 00:13:50 -0400 Original-Received: by mail-ot1-f50.google.com with SMTP id s20-20020a056830439400b0060c3e43b548so9811462otv.7 for <51766@debbugs.gnu.org>; Mon, 20 Jun 2022 21:13:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=Mf4W25bG2HkjNbpF3A2eIlJLCf3u4kmiIFfRxiBO0uw=; b=bBzwcY2a63SyAbWBgw+qmjfe9MVmuf7K+WjTa19w6cH+XQU9wcyuTl1Z6lo3HiizpD C1Akg7JEHi5mcmNubMmQctQpNgrHLLQHx1FcWuRe5J0UZB4U8kQ47NgzDcNpfKxOOdXV VagtFe7Zz4hhsTaQG/R032xEpNJEs0NMxNHwOr3k7ueXdonxoCgSw8t7yJMqDx7ebmxI Z1/Vxs3vg2EaRXe58RtD9+hQtTGOT1kfVhU7a2Ny9weXarSTmzeXng3iCh6koflalQYC q+DJVgUXs9oaLZgmVPOxBuVpvHaixy/936sN4qUnYZWUvz3thZxmQ6B+nBdS+GrOHiR8 w5Wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=Mf4W25bG2HkjNbpF3A2eIlJLCf3u4kmiIFfRxiBO0uw=; b=nX5VxXyaOFM6zkof1QXNsWY7tdll/jmO1PwqWdpUAoDEg/TMb8QEFyJmi4KHPNrGkE fz5IKfd+jLtohwAWrsg+yauk2j9mQkYgE0kTaCqKQvvQgyhmD28ENjBtdGSXULEr6X7y RRxet9vtyphZF5Ng8Dc9gCM8zguzVGtpqyPtqiGVwJ6eigZ0R5T4OQHYqs7yidxGeCiO kT3cFcc2X1scedvpzEruCwIwWBB7FeKXTf3y3dLVuMZz5A8cRGUvEpxYa1XJ4+8VssZ7 Xa7+5wb01NeIsWhtKHR+ZbZgGVuw0g7fb7t1HMXDRfuRxoHEXauCmtn5YJdWPGqfB1L7 cPFQ== X-Gm-Message-State: AJIora8Od5aYQQ1NzZQP9TQEf4DQHGnVO8fkcGiwYEJYJlwSF329v0SM 49f2HbqqwPjd1zWY8XNiUE69J2quWzi6jQ== X-Google-Smtp-Source: AGRyM1tDRJjNpaHXZffvaA2/uypcRQhtXu2LCevxe0oG7ciacxtk6IuZbVf6O7bH+ZvdqPAtqzIfgw== X-Received: by 2002:a05:6830:2a01:b0:606:d153:1ba0 with SMTP id y1-20020a0568302a0100b00606d1531ba0mr11322241otu.35.1655784822972; Mon, 20 Jun 2022 21:13:42 -0700 (PDT) Original-Received: from localhost ([207.126.88.10]) by smtp.gmail.com with ESMTPSA id m186-20020aca3fc3000000b00328c9e63389sm8437885oia.11.2022.06.20.21.13.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Jun 2022 21:13:42 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:234929 Archived-At: Stefan Monnier writes: >> See the above. There is real-world code doing things that make >> Emacs ignore after-change-functions. > > I don't see how this relates to what I'm saying: what I'm saying is that > for the same reason there's code that has very valid reasons to inhibit > `after-change-functions`, there will be code that has very valid reasons > to inhibit some new `after-really-every-change-functions`, and then > there will inevitably also be code that abuses this. > > The only real solution is to "push back" and get those abuses fixed. > > One thing you could do, for example is replace your char-modified-tick > check with one based on buffer-size: it won't catch all cases, but it > won't suffer from false positives, so you can really scream bloody > murder when it happens. Checking the buffer-size is a great idea. Thanks! It should be reliable enough for Org purposes. Best, Ihor