From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: "larsi@gnus.org" <larsi@gnus.org>, "rms@gnu.org" <rms@gnu.org>,
"46627@debbugs.gnu.org" <46627@debbugs.gnu.org>
Subject: bug#46627: [External] : bug#46627: [PATCH] Add new help command 'describe-command'
Date: Sat, 20 Feb 2021 20:35:28 +0000 [thread overview]
Message-ID: <CO1PR10MB4466E6EBDF7E0058565B9BE7F3839@CO1PR10MB4466.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83blcezntj.fsf@gnu.org>
> AFAIR, Emacs never meant completion to be a means of discovery.
> The discovery was always meant to be through "apropos" commands.
Emacs never originally meant a lot of things that
were later expanded (or repurposed to some degree)
to advantage.
This is normal for many processes of change.
Exaptation:
https://en.wikipedia.org/wiki/Exaptation
Spandrel:
https://en.wikipedia.org/wiki/Spandrel_(biology)
> > So the idea is to combine searching for commands
> > with looking up their documentation.
>
> I'm not sure this is a good idea, FWIW. For starters, it is limited:
> if you spot a command whose name sounds relevant, you have no simple
> way getting details about it. Unlike apropos commands, which do
> provide such ways.
"You have no such simple way" ... until you do.
Icicles (and I'm sure some other 3rd-party code
that enhances completion) can provide help on
individual completion candidates.
When completion candidates are things that have
doc strings, Icicles shows the first line of the doc
string for the "current" completion candidate in the
mode-line of the *Completions* window. When you
cycle among some candidates, you see their help there.
And you can hit a key to see the complete doc string
for the current candidate (it's shown in *Help*).
You mention apropos commands. They're great in part
because they allow keyword & regexp matching. This
is also true for Icicles completion. You can use
`M-x' with a regexp pattern as input, to see all
commands whose names match. And thus, to also get
access to their doc.
And unlike apropos, you can quickly change the match
pattern. And you don't need to scan a long list of
output when you're only interested in the doc of
this, that, or the other matching name.
It's not that this is _better_ than apropos. It's
different. Each has advantages, just as `occur'
and Isearch have different advantages.
Is the _purpose_ of `M-x' to invoke a command?
Sure - or not. Because you can _also_ use it to
browse command doc (and in other ways, not
mentioned), you can, if you want, sometimes use it
just for that - not bothering to invoke any command.
"Emacs never meant..." Emacs never intended...
Right. But now it does - at least with some
3rd-party packages.
next prev parent reply other threads:[~2021-02-20 20:35 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 1:06 bug#46627: [PATCH] Add new help command 'describe-command' Stefan Kangas
2021-02-19 8:42 ` Eli Zaretskii
2021-02-19 17:42 ` Stefan Kangas
2021-02-19 18:38 ` bug#46627: [External] : " Drew Adams
2021-02-20 3:25 ` Stefan Kangas
2021-02-20 4:25 ` Drew Adams
2021-02-20 8:20 ` Eli Zaretskii
2021-02-20 7:44 ` Eli Zaretskii
2021-02-19 20:05 ` Eli Zaretskii
2021-02-20 4:10 ` Stefan Kangas
2021-02-20 8:18 ` Eli Zaretskii
2021-02-20 17:10 ` Stefan Kangas
2021-02-21 13:08 ` Lars Ingebrigtsen
2021-02-22 15:58 ` Eli Zaretskii
2021-04-28 13:58 ` Stefan Kangas
2021-04-28 14:17 ` Stefan Kangas
2021-05-02 13:14 ` Stefan Kangas
2021-02-20 12:56 ` Lars Ingebrigtsen
2021-02-20 12:59 ` Eli Zaretskii
2021-02-20 16:16 ` Eli Zaretskii
2021-02-20 14:04 ` Stefan Kangas
2021-02-20 16:06 ` Richard Stallman
2021-02-20 16:09 ` Eli Zaretskii
2021-02-20 20:06 ` bug#46627: [External] : " Drew Adams
2021-02-20 20:17 ` Eli Zaretskii
2021-02-20 20:54 ` Drew Adams
2021-02-20 16:39 ` Stefan Kangas
2021-02-20 16:49 ` Eli Zaretskii
2021-02-20 20:35 ` Drew Adams [this message]
2021-02-20 20:46 ` bug#46627: [External] : " Eli Zaretskii
2021-02-20 21:16 ` Drew Adams
2021-02-21 15:07 ` Eli Zaretskii
2021-02-21 17:55 ` Drew Adams
2021-02-21 18:11 ` Eli Zaretskii
2021-02-21 18:30 ` Drew Adams
2021-02-26 21:34 ` Drew Adams
2021-02-27 8:04 ` Eli Zaretskii
2021-02-27 17:46 ` Drew Adams
2021-02-21 6:19 ` Richard Stallman
2021-02-21 7:18 ` Stefan Kangas
2021-02-21 15:27 ` Eli Zaretskii
2021-02-21 16:39 ` Howard Melman
2021-02-21 18:01 ` bug#46627: [External] : " Drew Adams
2021-02-21 17:01 ` Stefan Kangas
2021-02-21 17:36 ` Eli Zaretskii
2021-02-21 18:02 ` Stefan Kangas
2021-02-21 18:21 ` Eli Zaretskii
2021-02-21 19:57 ` Dmitry Gutov
2021-02-21 20:13 ` Eli Zaretskii
2021-02-21 23:46 ` Dmitry Gutov
2021-02-22 15:18 ` Eli Zaretskii
2021-02-27 20:38 ` Dmitry Gutov
2021-02-28 17:27 ` Eli Zaretskii
2021-02-28 21:40 ` Dmitry Gutov
2021-03-01 6:05 ` Eli Zaretskii
2021-03-02 1:40 ` Dmitry Gutov
2021-03-02 5:31 ` Eli Zaretskii
2021-03-02 12:55 ` Dmitry Gutov
2021-03-02 13:47 ` Eli Zaretskii
2021-02-21 17:57 ` bug#46627: [External] : " Drew Adams
2021-02-21 17:33 ` Drew Adams
2021-02-21 13:06 ` Lars Ingebrigtsen
2021-02-21 6:27 ` Richard Stallman
2021-02-21 6:10 ` Richard Stallman
2021-02-21 6:27 ` Richard Stallman
2021-02-19 13:12 ` Lars Ingebrigtsen
2021-02-19 18:27 ` bug#46627: [External] : " Drew Adams
2021-02-19 18:43 ` Eli Zaretskii
2021-02-21 6:18 ` Richard Stallman
2021-02-21 6:27 ` Richard Stallman
2021-02-20 6:56 ` Richard Stallman
2021-02-20 7:14 ` Stefan Kangas
2021-02-21 6:19 ` Richard Stallman
2021-02-21 6:27 ` Richard Stallman
2021-02-21 7:17 ` Stefan Kangas
2021-02-22 6:23 ` Richard Stallman
2021-02-24 3:28 ` Stefan Kangas
2021-02-27 18:58 ` Dmitry Gutov
2021-03-01 5:18 ` Richard Stallman
2021-03-01 16:13 ` bug#46627: [External] : " Drew Adams
2021-03-02 6:29 ` Richard Stallman
2021-03-02 6:50 ` Eli Zaretskii
2021-03-03 5:55 ` Richard Stallman
2021-03-03 15:26 ` Drew Adams
2021-03-03 16:14 ` Eli Zaretskii
2021-03-02 16:52 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO1PR10MB4466E6EBDF7E0058565B9BE7F3839@CO1PR10MB4466.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=46627@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.