unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Peter Dyballa <Peter_Dyballa@Web.DE>, 52435@debbugs.gnu.org
Subject: bug#52435: 29.0.50; C-y seems to contain an old contents
Date: Fri, 14 Jan 2022 10:34:46 +0100	[thread overview]
Message-ID: <87r19aoe2x.fsf@gnus.org> (raw)
In-Reply-To: <874k7a8pj4.fsf@web.de> (Michael Heerdegen's message of "Wed, 15 Dec 2021 05:23:27 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> I know too little about this to judge which behavior is expected and
> correct and would like to leave the decision to other more knowledgeable
> people.

If I understand correctly, the issue is whether `C-x o' should
deactivate the mark?  It seems like it did this in the olden times, but
it doesn't do this now?

I think the current behaviour makes sense, so I'd rather not change it
back -- I can't recall seeing any other complaints about this, and Emacs
has worked this way for at least some years now.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-01-14  9:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 14:58 bug#52435: 29.0.50; C-y seems to contain an old contents Peter Dyballa
2021-12-12  5:47 ` Lars Ingebrigtsen
2021-12-12 11:18   ` Peter Dyballa
2021-12-13  2:30     ` Michael Heerdegen
2021-12-13  9:07       ` Peter Dyballa
2021-12-14  8:48         ` Michael Heerdegen
2021-12-14  9:31           ` Peter Dyballa
2021-12-14 10:59             ` Michael Heerdegen
2021-12-14 11:15               ` Peter Dyballa
2021-12-14 12:13                 ` Phil Sainty
2021-12-14 14:02               ` Peter Dyballa
2021-12-15  4:23                 ` Michael Heerdegen
2022-01-14  9:34                   ` Lars Ingebrigtsen [this message]

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=87r19aoe2x.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52435@debbugs.gnu.org \
    --cc=Peter_Dyballa@Web.DE \
    --cc=michael_heerdegen@web.de \
    /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).