Hacker News new | ask | show | jobs
by aeturnum 925 days ago
I think the thing being criticized is the tenor of the pushback. The suggestion that, because the blog author (Eshel Yaron)'s patch wasn't accepted and the change is still currently in, that the maintainers are "insistent not to budge" and that this "demonstrates clear disrespect for Emacs user preferences, and indeed their freedom."

The Yaron's attitude seems to suggest that there's an easy right answer here and that it's the thing he wants (and Emacs does now). A lot of his upset seems not to be about the idea of an option to support the new behavior (which he wrote a patch to support!), but about the attitude with which this was introduced. In return, he's coming at this issue with an attitude that seemed fit to match what he thinks the maintainers are bringing.

So that's why it's important to ask if this blog post has misunderstood the arc of changes to Emacs. If the pushback will probably result in the current default staying in the editor. Because assuming the old behavior is best, even though some maintainers like the new behavior, is just as high handed as forcing the new behavior.

1 comments

There is actually an easy answer. There is a bug:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66394

The bug's description is this:

"When using `copy-to-register`, it is hard to see which register is already taken in the preview buffer."

If Eshel Yaron's simpler patch is enough to close 66394, and doesn't break anything, that should be used.

Generally speaking.