From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 48478@debbugs.gnu.org
Subject: bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer
Date: Sun, 06 Jun 2021 08:52:27 +0300 [thread overview]
Message-ID: <83sg1vilpg.fsf@gnu.org> (raw)
In-Reply-To: <87pmx03sg1.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 06 Jun 2021 00:35:58 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 48478@debbugs.gnu.org
> Date: Sun, 06 Jun 2021 00:35:58 +0300
>
> I don't disagree. I simply don't know what to do. For example,
> above you said to insert one of these two, but which one and how
> is completely unclear. So it seems we need to hear more opinions.
I think the conclusion up-thread was that if the entry is edited
before it's inserted, then the edited entry should be added to the
head of the kill-ring, and the pointer set there. IOW, if I edit the
previous kill and insert it, the edited string becomes the one I get
on the next C-y. The discussion concluded that doing this is possible
without extensive changes, whereas the other alternative is "hard" as
it goes against the current design and implementation of the functions
involved in this. I'm okay with this behavior, and it is easy to
describe in the manual and easy to remember.
next prev parent reply other threads:[~2021-06-06 5:52 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
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 [this message]
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=83sg1vilpg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48478@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).