[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer
From: |
Eli Zaretskii |
Subject: |
bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer |
Date: |
Sat, 22 May 2021 09:41:46 +0300 |
> From: Juri Linkov <juri@linkov.net>
> Cc: 48478@debbugs.gnu.org
> Date: Fri, 21 May 2021 21:18:33 +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.
It doesn't look like that in my testing. Here's the recipe:
emacs -Q
For the words "buffer", "text", "Lisp", and "evaluation" from the
first line, mark each word and then M-w
M->
M-y
Type "tex TAB", which will expand to "text"
Type "oize RET", which will insert "textoize"
Type C-y
This inserts the last kill, which is "evaluation", whereas I
expected to see "text", since you said the pointer stays at the
same position.
What am I missing here?
> > 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.
OK.
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, (continued)
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/18
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/19
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/20
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/20
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/20
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/20
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/20
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/20
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/21
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/21
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer,
Eli Zaretskii <=
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/22
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/23
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/25
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/26
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/26
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/27
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/30
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Eli Zaretskii, 2021/05/31
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/31
- bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer, Juri Linkov, 2021/05/30