Re: Proposal: new default bindings for winner and windmove

[Daniel Colascione]

On June 23, 2024 10:15:59 AM EDT, Po Lu <luangruo@yahoo.com> wrote:
>Daniel Colascione <dancol@dancol.org> writes:
>
>> I don't trust that many such users exist, and even if they did,
>> providing default keybindings for these keys will not somehow override
>> the keybindings you install yourself.
>
>Sure.  And more users stand to benefit from Windmove commands if they
>are bound to C-x 4, than if they were required to bind such commands
>themselves, commands defined by a package that is already of marginal
>interest?  What extraordinary logic!

Well, yes? It's of marginal interest because it's not discoverable. It's 
nevertheless useful. More people would use the package if it were discoverable. 
I don't think the logic is terribly complicated here.


>> This attitude is why Doom Emacs exists. A live software project is one
>> that changes. A dead one prioritizes stasis over user experience.
>
>Since Doom Emacs exists and is Free Software, why are users not at
>liberty to install it and bid farewell to reaction and "stasis" in Emacs
>development?  And why is it a matter for our consideration whether we
>fail or succeed in competing with them?  Any mention of "competition"
>with an Emacs package is already a contradiction in terms.

It continues to astound me that people want to put many hours into a project 
yet insist they're indifferent between its success and failure.

>> Nothing we're talking about here will disturb your custom
>> keybindings. Your experience will work just as it did before. The only
>> difference is that users who don't have custom bindings for the arrow
>> keys under C-x 4 will get windmove functionality if they don't
>> customize the bindings.
>
>Spoken like a true intellectual, in the face of a real-life example to
>the contrary.

I'm waiting for such an example. You've bound C-x 4 down to something. Fine. 
That binding would continue to work if Emacs came with C-x 4 already bound to 
something else. That's how defaults work. Can you please explain the actual 
problem that providing these new default bindings would cause for your workflow?