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

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

[Pedro Andres Aranda Gutierrez]

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

Hi

> Eduardo Ochs <eduardoochs@gmail.com> writes:

>> (setq register-use-preview 'never)
>> This is the wanted behavior when you are about to overwrite a register.

> It really is not.  The whole story of registers, since its dawn, was
> to have a very quick way of setting them.  That includes overwriting
> them quickly, this is specially important in keyboard macros

A big +1 here. The idea of register-use-preview is good, the name for the
behaviour, i.e. never,
also, but the implementation is not what I would expect. So maybe this
'never should bring back the old behaviour

Furthermore, and once that is fixed, I'd say that this should be the
default behaviour for a couple of cycles and have people opt-in for
(setq register-use-preview t)
in their init.el

My.002 c,
/PA

-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with two Juju logs:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 1613 bytes --]