[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changes for emacs 28

From: Dmitry Gutov
Subject: Re: Changes for emacs 28
Date: Sat, 12 Sep 2020 14:51:19 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

On 12.09.2020 09:12, Eli Zaretskii wrote:
Cc: rekado@elephly.net, ghe@sdf.org, emacs-devel@gnu.org,
From: Dmitry Gutov <dgutov@yandex.ru>
Date: Sat, 12 Sep 2020 00:00:48 +0300

As long as we keep this on the menu and the tool bar, there will be no
reason for a "war".

So there will be contradiction between the menu and the keyboard?

Yes.  We already have quite a few of them, so one or two more cannot

I'm looking to improve the current state of affairs.

Also: confusion about certain basic operations are likely to hit new users harder than confusions about other things.

How can it be confusing that 2 different commands produce different
results?  Why isn't it confusing today, when we already have these 2

The menu item doesn't exactly say which command it is invoking.

It does, if you invoke "C-h k".

Irrelevant, as long as we're talking about new user experience.

If you don't ask Emacs what the menu item invokes, then the text of
the menu item and the help-echo string are the only description you
get, and that is so for all the other menu items.  So there's nothing
new here.

Hence we shouldn't create a confusing menu item like this.

So I think that statement is missing the point: we should endeavor for
predictable and consistent sets of menu items, key bindings, and other

I agree, but the criteria for "predictable and consistent" might be
something other than "make the keybindings and menus invoke identical
commands".  Because if that's the criteria, we are already in
violation of them.

That doesn't mean we're not allowed to improve things in specific cases.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]