bug#48478: 28.0.50; yank-from-kill-ring and kill-ring-yank-pointer

[Juri Linkov]

>> This is an unfinished feature, i.e. currently yank-from-kill-ring
>> simply has no special handling of kill-ring-yank-pointer.
>> When I tried to add it, I noticed that it has many possible
>> variants of implementation, so I stuck with analysis paralysis.
>
> Why do we need variants? why not simply do the same as M-y does after
> C-y or M-y?  After all, from the user's POV it's the same command, so
> why not provide a consistent behavior?

No one objected until now, so there are users who prefer the current behavior.
But I don't disagree with changing the default to use kill-ring-yank-pointer.

>> A FIXME from 7b82584c69 is implemented by this patch:
>
> Thanks, I think you should install this.

Installed.

>> -(defun read-from-kill-ring ()
>> +(defun read-from-kill-ring (prompt)
>>    "Read a `kill-ring' entry using completion and minibuffer history."
>
> Please update the doc string to mention PROMPT.

Done.