|
From: | Dmitry Gutov |
Subject: | Re: Suggested experimental test |
Date: | Tue, 23 Mar 2021 16:00:44 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 |
On 23.03.2021 15:27, Philip Kaludercic wrote:
Dmitry Gutov <dgutov@yandex.ru> writes:On 23.03.2021 14:41, Eli Zaretskii wrote:But eventually, the intent is to change the default behavior, because rebinding any key to any command is already possible, and nothing prevents users from doing that in their private init files. So having a non-default theme that makes a bunch of such rebindings makes little sense to me.I think the above is more important than the goal of making it a default (which might or might not happen in 10 years or so, if we end up reaching some critical mass of users who dislike Emacs's historical bindings). But even while the alternative keybindings theme is not the default, we would maintain it and keep it usable. Whenever we add something to the default set, we would consider adding a corresponding binding to that other theme, etc.You mean new default commands, right?
Yup. Or other changes in the default set (moves, removals, replacements).
Having an alternative, well-considered set of bindings which new user can just toggle on and get comfortable should be valuable.Yes, this was my understanding too. Ideally, the splash screen could instruct new users how to change the UX theme, making it easier to get comfortable.
Some initial screen could do that, yes. Or at least we would tell about in the same places we mention cua-mode now.
[Prev in Thread] | Current Thread | [Next in Thread] |