unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 52435@debbugs.gnu.org
Subject: bug#52435: 29.0.50; C-y seems to contain an old contents
Date: Tue, 14 Dec 2021 10:31:56 +0100	[thread overview]
Message-ID: <E8A3B05E-AE36-4FCE-9CF4-B3AC89473DE2@Web.DE> (raw)
In-Reply-To: <87tufb1shx.fsf@web.de>


> Am 14.12.2021 um 09:48 schrieb Michael Heerdegen <michael_heerdegen@web.de>:
> 
> Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> 
>>> Do I understand correctly: you expect that C-x o deactivates the mark,
>>> but it doesn't?
>> 
>> It's exactly this for me surprising behaviour.
> 
> And you are sure that this was different in older emacs versions, and
> not just something in your config?  If you are, do we know when this
> changed?

No, I am not sure. IMO the documentation states that the mark will be cleared when I leave the buffer. (Or use M-< or M->.)

My usual behaviour is that I mark a region in *shell* buffer and apply shell-command-on-region. Then I move into another buffer in the same frame, mostly *compilation*. I perform a few edits on *Shell Command Output*, kill the remaining line and the buffer, and am back in *compilation* where I can use the edited output from *Shell Command Output*. Because a compilation was going on, I chose to use *shell* buffer to change from it to *Shell Command Output* and fell back to it. The region was still marked and so the contents of last kill-line in *Shell Command Output* was overwritten with the contents of the marked region. After C-y, seeing the wrong contents, I could Esc-y to bring back the killed line. So GNU Emacs worked transparently, only I was surprised about the unexpected contents.

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. (There I too work with MacPorts to keep some utilities and OpenSSL up-to-date and have to use the described procedure much more often, since some open software ports do not support the old OS and hardware and have to be excluded from upgrading at least initially.) If you can give me some variable names I can check whether I reset the original setting.

One fact should be stated: using a mouse click to change into another buffer clears the mark.

--
Mit friedvollen Grüßen

  Pete

Math illiteracy affects 7 out of every 5 Americans.






  reply	other threads:[~2021-12-14  9:31 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 [this message]
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

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=E8A3B05E-AE36-4FCE-9CF4-B3AC89473DE2@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=52435@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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).