From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48478@debbugs.gnu.org
Subject: bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer
Date: Fri, 21 May 2021 21:18:33 +0300 [thread overview]
Message-ID: <87h7iwuf0m.fsf@mail.linkov.net> (raw)
In-Reply-To: <83cztkocqt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 May 2021 08:51:54 +0300")
>> It would be unexpected when yanking the edited entry with M-y
>> would add it to the kill-ring as its opposite command M-w does.
>
> Why unexpected? If we document that, it wouldn't be unexpected.
>
> Once again, we could decide to either add the edited entry to
> kill-ring or not add it. If we don't add it, kill-ring-yank-pointer
> should stay at its position, which corresponds to the original entry
> before the editing. If we do add it, the pointer should be reset to
> the slot where the edited entry is. Both of these behaviors can be
> easily documented and will be reasonably logical and intuitive,
> because they are basically similar to what the old M-y did. What we
> do now is much harder to explain and is not intuitive, at least not
> according to my intuition.
For the case of not adding the edited entry to the kill-ring,
now kill-ring-yank-pointer stays at the same position it was
before the editing.
> Does anyone else have an opinion about this?
Regarding the question whether to add the edited entry to the kill-ring,
let's hear more opinions.
next prev parent reply other threads:[~2021-05-21 18:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 11:34 bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer Eli Zaretskii
2021-05-17 14:35 ` Lars Ingebrigtsen
2021-05-17 21:10 ` Juri Linkov
2021-05-18 11:51 ` Eli Zaretskii
2021-05-18 20:24 ` Juri Linkov
2021-05-19 2:30 ` Eli Zaretskii
2021-05-19 16:31 ` Juri Linkov
2021-05-20 9:32 ` Eli Zaretskii
2021-05-20 18:02 ` Juri Linkov
2021-05-20 19:04 ` Eli Zaretskii
2021-05-20 19:56 ` Juri Linkov
2021-05-20 20:10 ` Eli Zaretskii
2021-05-20 20:44 ` Juri Linkov
2021-05-21 5:51 ` Eli Zaretskii
2021-05-21 18:18 ` Juri Linkov [this message]
2021-05-22 6:41 ` Eli Zaretskii
2021-05-22 20:59 ` Juri Linkov
2021-05-23 7:19 ` Eli Zaretskii
2021-05-25 20:35 ` Juri Linkov
2021-05-26 12:05 ` Eli Zaretskii
2021-05-26 22:09 ` Juri Linkov
2021-05-27 7:30 ` Eli Zaretskii
2021-05-30 22:32 ` Juri Linkov
2021-05-31 12:08 ` Eli Zaretskii
2021-05-31 20:20 ` Juri Linkov
2021-06-01 12:13 ` Eli Zaretskii
2021-06-01 20:32 ` Juri Linkov
2021-06-02 14:57 ` Eli Zaretskii
2021-06-02 21:10 ` Juri Linkov
2021-06-03 6:19 ` Eli Zaretskii
2021-06-03 20:55 ` Juri Linkov
2021-06-04 5:57 ` Eli Zaretskii
2021-06-04 16:46 ` Juri Linkov
2021-06-04 19:04 ` Eli Zaretskii
2021-06-05 21:35 ` Juri Linkov
2021-06-06 5:52 ` Eli Zaretskii
2021-06-06 20:52 ` Juri Linkov
2021-06-07 12:16 ` Eli Zaretskii
2021-06-08 16:55 ` Juri Linkov
2021-06-10 12:07 ` Eli Zaretskii
2021-06-11 17:10 ` Juri Linkov
2021-06-11 18:06 ` Eli Zaretskii
2021-06-11 18:33 ` Juri Linkov
2021-06-11 19:23 ` Eli Zaretskii
2021-06-11 19:16 ` Eli Zaretskii
2021-05-30 22:23 ` Juri Linkov
2021-05-31 12:04 ` Eli Zaretskii
2021-05-31 20:17 ` Juri Linkov
2021-06-01 12:12 ` Eli Zaretskii
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=87h7iwuf0m.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=48478@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).