From: Arthur Miller <arthur.miller@live.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: me@wilfred.me.uk, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Helpful in Emacs?
Date: Thu, 09 Sep 2021 14:35:47 +0200 [thread overview]
Message-ID: <AM9PR09MB4977AF3D5B2D213D6A26E8CE96D59@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <CADwFkm=e6bp5K1caKyhSbyqA-6kjKg7QS-Fnwo9h2w9wcBLiiw@mail.gmail.com> (Stefan Kangas's message of "Thu, 9 Sep 2021 13:34:18 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> Arthur Miller <arthur.miller@live.com> writes:
>
>> Any chance of getting Helpful, https://github.com/Wilfred/helpful, into official
>> Emacs? In the contributor list I see some familiar names which already
>> contributed to Emas, so they have signed FSF papers, but also some unkown ones
>> too.
>
> FWIW, here's my take on this:
>
> 1. helpful.el has several useful features. They should be evaluated
> one by one with the aim to integrate them in a clean way into the
> built-in help.el et al libraries. Such an evaluation would likely
> show that some features are well suited for the default help system.
> Maybe others we would want as optional features. Maybe other features
> still are better left in an external package.
>
> 2. Doing the above job well would presumably leave little reason to
> distribute helpful.el together with Emacs.
A week or two ago I was actually looking at Emacs help code. I wanted to bring
in the source code as well as references into help lookup, but honestly, I would
rather prefer to just include helpful instead of re-implementing everything. If
the authors have signed the paperwork, I see no reason why not just include
it. Also original help lookup could be left as low-resource, faster solution for
people who prefer to spend less resources on help lookup, while helpful could be
enabled by a custom variable, something like show extended help or as a minor mode.
> 3. Before we can even start thinking of doing any of this, we will
> need to sort the copyright assignments. This to my mind means that
Yes. That was my thought, I wanted to check is there is interest from emacs devs
and I have CC-ed Willfred because he is the only one that can answer the
paper-status I guess, and if there is interest from his and other helpful-devs
side to get this included.
> need to sort the copyright assignments. This to my mind means that
> the next step to make meaningful progress here is to get the module
> onto GNU ELPA. Once that is done, points 1 and 2 are mostly "only" a
> matter of copying in the code.
>
> If you would like to work together with the helpful.el maintainers to
> get the package onto GNU ELPA, that would be worthwhile and
> appreciated, I think.
I'll help with what I can of course, but I am probably not of much help here. I
have never contributed to Elpa myself :).
By the way, there are probably no problems of getting Helpful into "Nelpa"
(non-gnu elpa), and it already is in Melpa, so the access for new users is not
far away. I would though really like to see it as a complement to built-in help
out of the box.
next prev parent reply other threads:[~2021-09-09 12:35 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 [this message]
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
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=AM9PR09MB4977AF3D5B2D213D6A26E8CE96D59@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--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).