Re: Please, Restore Previous Behavior for jump-to-register

[Thierry Volpiatto]

Thierry Volpiatto <thievol@posteo.net> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Which situations currently require a RET when register-use-preview is
>> set to 'never'?
>
> The only situations are when you overwrite a register or when you modify
> it (increment etc..), this with the three options register-use-preview
> propose.
>
> I think it is important to have a kind of warning and confirm when doing
> so.  I have personally often overwrited registers I was working with
> inadvertantly.
>
> After reading the complaints here, I have the impressions most of those
> people had build a workflow based on really few registers because it was
> hard with previous UI to figure out which one to use.
>
> Now when you set a new register you can use M-n and there it will set
> the register without the need to press RET.
>
> I think the current behavior is sane, specially for new users - it is
> really surprizing that when hitting "a" for example there is no
> confirmation at all -, so I think the default for register-use-preview
> should be `t`.
>
> If needed I can disable RET easily for register overwrite as well, this
> for the two remaining options of register-use-preview (nil and 'never)
> but I think it would be an error.
>
> Eli let me know what you think is the best option.
>
> Thanks.

Note also that in addition to register-use-preview setting, one can use

    (cl-defmethod register-preview-command-info ((_command (eql 
copy-to-register)))
      (make-register-preview-info
       :types '(string number)
       :msg "Set register `%s'"))

to have the wanted behavior (no RET when overwriting) for
copy-to-register command.

-- 
Thierry

signature.asc
Description: PGP signature