[entropie]

> Since then, another bug report came in from a Emacs master branch user that suffered from one of the consequences of this change (a specific regression that I spelled out days before, but was ignored, for some reason), and several users reached out to the Emacs development in request to restore the previous behavior in an ongoing thread titled “Please, Restore Previous Behavior for jump-to-register”. Astonishingly, Eli and Thierry won’t seem to budge, and Emacs 30 will thus likely suck.

Seriously, this is kind of funny. I use emacs for like two decades now and I knew about jump-to-register but never actively used it. But yes - emacs 30 will be bad because of this change. Barely useable anymore. This guys in their mailinglist have... very specific problems.

You heard it first here. Emacs 30 will suck.

Also; https://xkcd.com/1172/ hits the spot and is - what a coincidence - about emacs and workflows.

[addicted]

I’m a VIM user, not an emacs user so I don’t have a dog in this fight, but if the equivalent change was made in VIM it would pretty much be unusable for me. My muscle memory related to this feature would be completely broken.

I can’t think of any such change in VIM being made without a setting to turn it off.

[tom_]

If you use this stuff a lot, it is totally going to suck. Some thing has changed, that may or may not have a good technical reason, that means that after years of the program training you into behaving one way (and it's not like this is some crazy workflow you've invented yourself, right - this is literally you following the documented process) you're now being punished for it by having it not work.

You wouldn't even treat your dog like this.

[kyrra]

While I understand your point, emacs is changing very specific behavior, that was intended, to do something new now. So I would say you're xkcd comment is slightly off.

[entropie]

> emacs is changing very specific behavior, that was intended, to do something new now

No? It changes how an existing command behaves.

> This commit crippled all user interaction with Emacs registers, turning commands such as C-x r s, once smooth and frictionless, into a cumbersome and painful mess. Concretely, instead of just typing the key for the register you want to operate on, you now get a fully blown minibuffer for inserting a single key.

[broscillator]

with all due respect c-x r s sounds far from smooth and frictionless to me

[monsieurbanana]

If you're so used to type C-x that you don't even register it, like most emacs users, then it's just pressing "r s" for "register save".

It's not terrible, and the mnemonic is sound. If you don't like it, perfectly valid opinion, you're just not made for emacs' default behavior.

[broscillator]

I can think of no instances where I need to press a key and a modifier, a key, and then another key, in any program. If I had any bindings like that in vim I remapped them.

I'm definitely not made for emacs, specially not its pinky :)

[mjw1007]

True. The traditional binding was was just `C-x x`, but they've already done one round of making register features more inconvenient to get at.

[Finnucane]

‘Frictionless’ here means ‘we’ve done it this way forever and don’t have to think about it anymore.’

[lvncelot]

I mean, we're talking about changing intended behavior here and not accepting any discussion regarding that. Just because you didn't use jump-to-register, doesn't mean no one does. Again, this is not people using unintended consequences of edge-case-behavior, this is people complaining (rightfully so) about regressions that stem from changing the intended UI.