From: Juri Linkov <juri@linkov.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: 36922@debbugs.gnu.org
Subject: bug#36922: [PATCH] Add defalias toolbar-mode for tool-bar-mode
Date: Mon, 09 Sep 2019 00:58:46 +0300 [thread overview]
Message-ID: <87ftl6qwkp.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkmnqMC7irQwss-TR0qRG0LC-21+d2EcWZca2Pdog5T81_A@mail.gmail.com> (Stefan Kangas's message of "Sun, 8 Sep 2019 22:57:30 +0200")
>> Oh, the name of the new feature tab-bar was modeled after tool-bar,
>> so now it should be renamed to tabbar, this doesn't look too nice.
>
> I think that should be "tab-bar", since that seems to be the most
> common spelling.
Indeed preparing good names for completion makes them easier to type.
For example, recently after adding the "tab-bar-mouse" command made harder to
enable "tab-bar-mode" by typing just "tab-b-mo", it doesn't complete anymore.
Also better would be to group all related commands under one prefix,
such as "tab-next", "tab-previous" for easier completion.
> I'm not suggesting a rename of "tool-bar" by the way, only a convenience alias.
Please try to find evidence that more people have the same problem
with completion. For example, I have in my init file such aliases
that I often mistype, e.g.:
(defalias 'comapre-windows 'compare-windows)
because "comapre" is easier to type than "compare" on a qwerty keyboard :)
Another solution is to make completion smarter, like when in bash
mistyping a shell command still find it by correcting its name.
next prev parent reply other threads:[~2019-09-08 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 17:41 bug#36922: [PATCH] Add defalias toolbar-mode for tool-bar-mode Stefan Kangas
2019-08-05 2:23 ` Drew Adams
2019-08-06 11:38 ` Stefan Kangas
2019-09-08 19:40 ` Stefan Kangas
2019-09-08 20:43 ` Juri Linkov
2019-09-08 20:57 ` Stefan Kangas
2019-09-08 21:58 ` Juri Linkov [this message]
2019-09-08 22:16 ` Stefan Kangas
2019-09-09 16:11 ` Eli Zaretskii
2019-09-09 17:19 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftl6qwkp.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=36922@debbugs.gnu.org \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).