81–90 of 250 posts
So, what's the "other side's" argument in this? Usually these opinionated changes come with some level-headed reasoning behind the changes. Or maybe not?
This is what I've been wondering here, as well. So far, the downsides (Change to an almost subconscious muscle-memory-task, added friction) of this are pretty apparent - what even are the upsides of this?
Earlier quoted context omitted.
It's explained in the article.
I’m not an Emacs user and also failed to understand what went wrong. So they changed a default shortcut or something?
Additionally, some actions on top of the original behavior (that depended on Ctrl-C completing automatically, to keep with the analogy), now are just broken.
This thread is mostly "I don't use this feature of Emacs (or Emacs at all) therefore this isn't a real problem, so stop complaining." Poor to see. I'd rather people who do regularly use the feature weigh in on how they feel about its new behavior.
Emacs should be about customization and changing such a basic feature without a way to return to the original behavior is pretty bad.
I'll summarize my understanding. A commit that changes how copying (actually "registers", which is a bit more general than copying) works in emacs was recently accepted. Now emacs opens up a minibuffer that shows what is happening, requiring one to accept the change by hitting enter or equivalent. The OP thinks this is a terrible, breaking change as it changes default behavior (and possibly without the possibility of…
?
I can’t tell what this comment is supposed to mean.
He disagrees; other people also felt similarly about it but, they were ignored.
They say, if you don’t like it, why don’t you contribute? …but he did and that wasn’t acceptable either, so he’s forked it.
Do you feel it’s out of order to walk your own path with free software if you disagree with the maintainers? Isn’t that the whole point of GNU?
Earlier quoted context omitted.
You’re missing the double quote before the ‘d’ which means you’re talking about a register.
Ah, thanks. You're right, my brain parsed the gp's comment as simply "dyy".
It seems like this option was mentioned before the original post was published, but perhaps the author didn't see this? I assume this would fix the issue, but I may be missing something.
--
EDIT: it looks like this will still require a RETURN keypress, based on the reply from ginko below.
I'll summarize my understanding. A commit that changes how copying (actually "registers", which is a bit more general than copying) works in emacs was recently accepted. Now emacs opens up a minibuffer that shows what is happening, requiring one to accept the change by hitting enter or equivalent. The OP thinks this is a terrible, breaking change as it changes default behavior (and possibly without the possibility of…
Muscle memory should be elevated to a first class concern when it comes to emacs.