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

[Eli Zaretskii]

> From: Juri Linkov <juri@linkov.net>
> Cc: bug-gnu-emacs@gnu.org
> Date: Tue, 18 May 2021 00:10:57 +0300
> 
> > Bug or feature?  If the latter, what is the rationale for the
> > different operation?
> 
> 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?

> Regarding 7b82584c69, actually the description of 'M-y' in
> (info "(emacs) Isearch Yank") was accurate.  It correctly
> described the behavior of isearch-yank-pop that activates
> the minibuffer.  The problem is that after recent controversy,
> 'M-y' was rebound to the backward-compatible command
> isearch-yank-pop-only.

The last sentence means that the description in the manual which I
deleted was indeed inaccurate: it described a binding that doesn't
exist by default.  NEWS does a better job by telling users to make
that binding if they want.  (I decided that saying the same in the
manual was too much: we don't describe optional keybindings unless
they are extremely useful/important.)

> A FIXME from 7b82584c69 is implemented by this patch:

Thanks, I think you should install this.

> -(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.