From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#52435: 29.0.50; C-y seems to contain an old contents Date: Tue, 14 Dec 2021 11:59:31 +0100 Message-ID: <87lf0n1mgc.fsf@web.de> References: <46037FBE-8DAB-4913-850C-96F4F78622E2@Web.DE> <877dcafk78.fsf@gnus.org> <8A9C7C2F-642A-454D-A99B-0945A1E2D5F7@Web.DE> <87fsqxjkx5.fsf@web.de> <0B5129BE-27A6-460A-ABE7-85A3504C55DE@Web.DE> <87tufb1shx.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1995"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Lars Ingebrigtsen , 52435@debbugs.gnu.org To: Peter Dyballa Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Dec 14 12:00:23 2021 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 1mx5Xi-0000Il-7I for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Dec 2021 12:00:22 +0100 Original-Received: from localhost ([::1]:38940 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mx5Xg-0002HB-Hb for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Dec 2021 06:00:20 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47860) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mx5XO-0002E3-UL for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 06:00:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46108) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mx5XO-0006Pz-Kq for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 06:00:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mx5XO-0004wX-J0 for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 06:00:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 14 Dec 2021 11:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52435 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 52435-submit@debbugs.gnu.org id=B52435.163947958018943 (code B ref 52435); Tue, 14 Dec 2021 11:00:02 +0000 Original-Received: (at 52435) by debbugs.gnu.org; 14 Dec 2021 10:59:40 +0000 Original-Received: from localhost ([127.0.0.1]:57654 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mx5X2-0004vT-Ds for submit@debbugs.gnu.org; Tue, 14 Dec 2021 05:59:40 -0500 Original-Received: from mout.web.de ([217.72.192.78]:38019) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mx5X1-0004vG-4f for 52435@debbugs.gnu.org; Tue, 14 Dec 2021 05:59:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1639479572; bh=AEwNfQ976BflKSN0CvX/45eLMaRpJ3Xu50YZJzMEdBM=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=DY6zqJILlK8mhDX0Jv6EXTYFp/UlrPMaoV8uDNxOiCw7gpcS/RCK+8W2o9Q3Qro3G QcEJSdE1SaBznlOG747bIUbpc0R6bg39DhZva8d1g1RrGnKsEdV1+pYGsIQMM06e9i 3cSASlzqDKW8UIIqKStdeDn+YQCXxL4Axwbf5MS8= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([92.208.225.87]) by smtp.web.de (mrweb106 [213.165.67.124]) with ESMTPSA (Nemesis) id 1Mvslx-1mhUO31Cdj-00sq2h; Tue, 14 Dec 2021 11:59:32 +0100 In-Reply-To: (Peter Dyballa's message of "Tue, 14 Dec 2021 10:31:56 +0100") X-Provags-ID: V03:K1:HtqwoA3m88teodi4pJMSPNB0xvzir44GaJ+SJ3vqDJtOmiAGDig bamPQQvjOe5wXKEEkFCfkI7yuQB6ImXKgd8eR/tomAuZgZGbos26AahrFPpA5xoMZgwdLq8 hGyCBrqs32wwJV2i7UYHR1U27lrjX3N1XCLJjPgmRdQW/PV96uifcUAEN75bWjkCwthAYz5 +XuLmHV7x7PxohBC6vWVw== X-UI-Out-Filterresults: notjunk:1;V03:K0:7ScX0YSJNRw=:q3rDLqAc95BKSEli604gfM 1xqZ4xqbAtlI947LaNQhNw0RCQS0ypKHCLMlxtqrK9d96uGy1J2EogQO50n+6+BMSmFjk8/jv LVob0uSZh/nhW92u8sjvr3O/nC/7+cxGSrPJRRCPo5O9pSTFQgMGrcy7JJsKsJX+E76Ur/baK gKhWPK4qnk1Og32iLpQE6oFK+N0Z7NRn6F9EB1iY+eH/ci2gD6ALdcxu3KIkyG0AS6t7fgXOV wRwCc/HoaKyjUMaseHojkEOcLwusZPV3n98erQBGrnO2EC3ir+UDahM9vRScKYlMzADY+yyd8 hz+5ppzx0MwbkdCgWVeEumGk2rk/5CDhnrB8HGZ0q2ApRGa19DXe3/6WXFM+OezKKUYLlDoVC 3tFhS00e7Tg/ehGFeIjE38UKNoaPzgUmAp3qDwOmTmHzD35IPc/Bqr4dOh1ytU77pN+ofU+xv Tf0WDDkJk02c40b2chYniG1EVaoJZR7X0CP1YPkbHPNtKF0IhMo3zCdbUkdd9GxWvbO8lOxRh 0ZqV0FAFF2ShcpX2UwBP062zYEa2FT9/OB+QSZyh4D5yLHtKGw7WfOiHOVjgsReHWE+fReTPK QaCTJkdTf32eo4nhB7Yi67ntQO77HRlXSUpE0hMklasnVV2idko9XzE9GgzQaEeM7KsHe88di 8xfI8ANKx6pUIt1xhnCYhJMjdIOUlBR8j/EcOkxP0n+ny1ME7qjMoHEcTOtiMiPdbJ47S+TF2 spJWgZAz7TMevTp6DP+Zs5+LDtyoFCNUyXlf7wOfpN7lP/B713hXux12YRTcIsiMdaJg5JBR 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:222362 Archived-At: Peter Dyballa writes: You wrote in an older message: > The documentation in GNU Emacs 26.1 seems to be clearer: > The mark is "deactivated" by changing the buffer, > and after certain other operations that set the mark but whose > main purpose is something else--for example, incremental search, > M-<, and M->. > And it states that the region is cleared when changing to another > buffer. I'm not sure if "changing the buffer" means "modifying the buffer" instead of "changing to another buffer". > I don't think that I have a particular configuration, except > (transient-mark-mode t). As I wrote on Sunday, a few older versions of > GNU Emacs show the same behaviour. On a decades old PowerBook I could > check the behaviour of much older Emacsen and report here. That would be interesting. > If you can give me some variable names I can check whether I reset the > original setting. What kind of variables do you mean? IIUC the behavior is not really depending on options. It's an implicit thing: commands set the variable `deactivate-mark', and the command loop checks this variable at the end of the execution of any command, and when it's non-nil it deactivates the mark. > One fact should be stated: using a mouse click to change into another > buffer clears the mark. This is done explicitly in `mouse-drag-track'. Dunno if it's intentional in this case. Michael.