From: Arthur Miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: me@wilfred.me.uk, stefan@marxist.se, mardani29@yahoo.es,
emacs-devel@gnu.org
Subject: Re: Helpful in Emacs?
Date: Fri, 10 Sep 2021 10:00:47 +0200 [thread overview]
Message-ID: <AM9PR09MB4977250454F95175672EAE0B96D69@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <83wnnoj3gz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Sep 2021 10:26:36 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arthur Miller <arthur.miller@live.com>
>> Date: Fri, 10 Sep 2021 09:11:19 +0200
>> Cc: me@wilfred.me.uk, Emacs developers <emacs-devel@gnu.org>,
>> Daniel Martín <mardani29@yahoo.es>
>>
>> So the alternative is to develop similar functionality ourselves into built-in help?
>
> Yes, but we need first to establish which features we want to have,
> which ones are opt-in and which opt-out, etc.
I just answered to Stefan K:
What I care most for at the moment are: doc lookup for autoladed functions
without the doc in the stub, and not yet loaded; and code inlined in help buffer,
instead of just plain link. The former would make it possible to save some
space, for example docs does not need to be included in stubs, and can be
fetched on demand. For example package-quickstart.el wouldn't need to pack 800
kb of docs when some of those will never be requested anyway.
The latter is just plain nice to have. It saves time if I can just scroll other
(help) buffer and read the source without need ot click on link in it to fetch
the source code.
next prev parent reply other threads:[~2021-09-10 8:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 10:57 Helpful in Emacs? Arthur Miller
2021-09-09 11:34 ` Stefan Kangas
2021-09-09 12:35 ` Arthur Miller
2021-09-09 15:21 ` Daniel Martín
2021-09-09 15:48 ` Arthur Miller
2021-09-10 6:20 ` Stefan Kangas
2021-09-10 7:11 ` Arthur Miller
2021-09-10 7:19 ` Stefan Kangas
2021-09-10 7:58 ` Arthur Miller
2021-09-10 8:14 ` Jean-Christophe Helary
2021-09-10 12:32 ` Stefan Monnier
2021-09-10 7:26 ` Eli Zaretskii
2021-09-10 8:00 ` Arthur Miller [this message]
2021-09-10 11:14 ` Eli Zaretskii
2021-09-10 11:41 ` Arthur Miller
2021-09-09 19:21 ` Eduardo Ochs
2021-09-09 19:51 ` Arthur Miller
2021-09-09 20:23 ` Arthur Miller
2021-09-09 22:55 ` Dmitry Gutov
2021-09-10 0:52 ` Arthur Miller
2021-09-10 6:16 ` Eli Zaretskii
2021-09-10 6:06 ` Eli Zaretskii
2021-09-10 6:21 ` Arthur Miller
2021-09-10 6:30 ` Juri Linkov
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=AM9PR09MB4977250454F95175672EAE0B96D69@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=me@wilfred.me.uk \
--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).