Re: select yank via completion

[Juri Linkov]

>> > And then where do we bitch at the user if he/she does want to yank
>> > into a read-only buffer?
>>
>> In the same place where 'C-x 8 RET' (insert-char) does this:
>> it has no "*" in the interactive spec, and allows using it
>> in read-only buffers to browse a list of character completions
>> with TAB, but exiting the minibuffer with RET signals the error
>> "Buffer is read-only" somewhere in the 'insert' functions.
>
> But that the function will behave differently if called via
> call-interactively with a non-nil 2nd argument, right?

(call-interactively FUNCTION &optional RECORD-FLAG KEYS)

  Optional second arg RECORD-FLAG non-nil
  means unconditionally put this command in the variable ‘command-history’.

So it's a good thing that this command will be added to ‘command-history’,
because then the user can switch to a non-read-only buffer and type 'C-x M-:'
to insert the previously selected character in a writable buffer.