From: John Wiegley <jwiegley@gmail.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Improving describe-mode and discoverability
Date: Wed, 06 Jul 2016 10:47:08 -0700 [thread overview]
Message-ID: <m2vb0ik6ar.fsf@newartisans.com> (raw)
In-Reply-To: <576C2A6C.3090908@gmail.com> ("Clément Pit--Claudel"'s message of "Thu, 23 Jun 2016 14:29:00 -0400")
>>>>> Clément Pit--Claudel <clement.pit@gmail.com> writes:
> What do you think? I would be happy to get help in refining this code (and
> this proposal). For example, we could consider hyperlinking the function
> names to their sources, or letting users expand the first line of the
> documentation to show the full docstring. We could also think about ways to
> cover functions that are not bound to a key by default, but which users may
> want to bind (e.g. by looking for interactive functions starting with the
> mode's name).
This is wonderful, Clément! However, I wouldn't change the behavior of
`describe-mode': I'd add a new function (in ELPA to begin with) called
`describe-mode-verbose', and then advise `describe-mode' so that, at the
beginning or end of the help buffer, a button appears leading one to that
information.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
prev parent reply other threads:[~2016-07-06 17:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 18:29 Improving describe-mode and discoverability Clément Pit--Claudel
2016-06-23 18:46 ` Robert Weiner
2016-06-23 18:52 ` Clément Pit--Claudel
2016-06-23 19:11 ` Robert Weiner
2016-06-23 19:36 ` Clément Pit--Claudel
2016-06-23 20:26 ` Drew Adams
2016-06-23 21:50 ` Clément Pit--Claudel
2016-06-23 22:07 ` Drew Adams
2016-06-23 22:10 ` Dmitry Gutov
2016-06-23 22:27 ` Clément Pit--Claudel
2016-06-23 23:15 ` Drew Adams
2016-06-23 23:39 ` Clément Pit--Claudel
2016-06-24 0:05 ` Drew Adams
2016-06-24 2:59 ` Clément Pit--Claudel
2016-07-06 17:47 ` John Wiegley [this message]
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=m2vb0ik6ar.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
/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).