From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#60467: 30.0.50; primitive-undo: Changes to be undone by function different from announced Date: Wed, 04 Jan 2023 18:16:07 +0000 Message-ID: References: <87o7ri74qv.fsf@localhost> <9bc9c69ac20a37ded741@heytings.org> <9bc9c69ac282c0148962@heytings.org> <87h6x9mgdv.fsf@localhost> <838rij23by.fsf@gnu.org> <83zgazznau.fsf@gnu.org> <83mt6yz7se.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18834"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 60467@debbugs.gnu.org, acm@muc.de, Eli Zaretskii , yantar92@posteo.net To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 04 19:17:44 2023 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 1pD8Ke-0004dR-6q for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 04 Jan 2023 19:17:44 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pD8KJ-0001xg-Sd; Wed, 04 Jan 2023 13:17:29 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pD8Jy-0001ul-Kc for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2023 13:17:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pD8Jx-0005Er-Sd for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2023 13:17:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pD8Jx-0003fE-Nv for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2023 13:17:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 04 Jan 2023 18:17:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60467 X-GNU-PR-Package: emacs Original-Received: via spool by 60467-submit@debbugs.gnu.org id=B60467.167285617114020 (code B ref 60467); Wed, 04 Jan 2023 18:17:01 +0000 Original-Received: (at 60467) by debbugs.gnu.org; 4 Jan 2023 18:16:11 +0000 Original-Received: from localhost ([127.0.0.1]:49542 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pD8J9-0003e4-IZ for submit@debbugs.gnu.org; Wed, 04 Jan 2023 13:16:11 -0500 Original-Received: from heytings.org ([95.142.160.155]:58878) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pD8J7-0003dv-3s for 60467@debbugs.gnu.org; Wed, 04 Jan 2023 13:16:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1672856167; bh=MeLF0FLNN0RlFdQvxLuDSXphzkYP83ASxWPobLFzgK0=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=D/y0+gppsxGW5zPIXYl5Zxm/TQdCc8llh5ecn7WmWMwn4guROaUOt+KTVeJHckaik ZJ3eKANuxRBjk15EkRbqq6+WnNNA9H3QrWgWy2HAM8lQGy0Tbm9iAICMJdkTAQ57Vi c1OJj9Ei4lTKoBg6ZX9Nvn0BcX+Px9WSHAzngnbwxiUTjRr0jrGDUYa/l8/eHGQOGA fn5y6BLk1hgVv3FeMccli73rmSJBMt8koYs3KUmGw7OcM3phliOYcS/Lc6cPaJJTzB kJwCQz2tYpOUNJ5r+tbNYGIvMfKUJfS6X3FatKXb9ImG/IiawmsYEgL0bVRungTUmq IHJoxV3932TAw== 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:252517 Archived-At: >> Well, I hope this tricky code will be replaced by the non-tricky code I >> proposed, in which none of these obscurities exist... ;-) > > My hope is that we can just remove the timestamp special case, in which > case we can keep the current code mostly unchanged. > Then our hopes are different. What's wrong exactly with replacing a piece of code that requires a long discussion with question marks everywhere to be understood by a piece of well-documented code that is much more readable and "evidently" does what it is supposed to do?