I am a Vim guy. Can someone explain what exactly is broken?
Bad NEWS, Emacs
11–20 of 250 posts
Re: Bad NEWS, Emacs
#12I am a Vim guy. Can someone explain what exactly is broken?
It's explained in the article.
Re: Bad NEWS, Emacs
#13It's a good rant, but it probably doesn't help its case that it doesn't stop to explain what the feature it's talking about actually is. Emacs registers are a really, really old abstraction. Registers are like separate clipboards, you can put stuff there and pull it out. And there are 62 of them (each associated with a core ASCII symbol: [a-zA-Z0-9]), giving you a lot of flexibilty and a very quick keyboard interface for acting on/with them. And you can even do fun stuff like execute a keyboard macro out of a register. Some people use them heavily. I don't.
Anyway the author is peeved that they changed the default bindings such that there's a modal UI in the way of what used to be a fully-keyboard/home-row operation. It sounds like a reasonable complaint; I'd be annoyed too if they changed something that lived in my muscle memory like this kind of feature does.
Re: Bad NEWS, Emacs
#14I don’t fully understand the nature/impact of the change but this conflict seems so minor to me. Like, people on both sides display the same level of entitlement but for different reasons, and they all think they have their are “right”. Hum, no, for outsiders you all appear stubborn and lacking ability to compromise. “Oh my gosh, I’ll have to press 1 extra key now, this project is doomed!”, “no no no, this little change is the hallmark of security, it should be mandatory for every user”. Come on…
Re: Bad NEWS, Emacs
#15I someone is to fork Emacs its because of getting proper UI integration or multithreading. This is just a neglectable, whimsical step. Sorry. What Emacs needs is the nvim/vim Schisma.
There was Xemacs back in the day… and I guess it is still around.
Re: Bad NEWS, Emacs
#16I someone is to fork Emacs its because of getting proper UI integration or multithreading. This is just a neglectable, whimsical step. Sorry. What Emacs needs is the nvim/vim Schisma.
> What Emacs needs is the nvim/vim Schisma.
It's already had like six, over the decades.
Re: Bad NEWS, Emacs
#17> 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.
Re: Bad NEWS, Emacs
#18This is really polemically overstating the case, but at least it links to the mailing list threads where you can see what's actually going on. Not that anyone will click them.
Re: Bad NEWS, Emacs
#19Re: Bad NEWS, Emacs
#20> 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,…
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.