unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: me@wilfred.me.uk, "Daniel Martín" <mardani29@yahoo.es>,
	"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Helpful in Emacs?
Date: Fri, 10 Sep 2021 09:58:18 +0200	[thread overview]
Message-ID: <AM9PR09MB49775A7AC0A3DB1B0D1A685996D69@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmnf8jiYSdh25ayM=+O6rR8mXte5eNHGMDXcEV_r9Zh8yg@mail.gmail.com> (Stefan Kangas's message of "Fri, 10 Sep 2021 09:19:29 +0200")

Stefan Kangas <stefan@marxist.se> writes:

> Arthur Miller <arthur.miller@live.com> writes:
>
>> After looking into the helpful code I realize it used s.el, dash.el and some
>> other libraries which are not part of Emacs, so I guess chances to get it into
>> Emacs are slim to none, since all those packages would also need inclusion.
>
> From helpful.el:
>
> ;; Package-Requires: ((emacs "25") (dash "2.18.0") (s "1.11.0") (f
> "0.20.0") (elisp-refs "1.2"))
>
> IIUC, "dash", "s" and "f" are just convenience libraries that could be
> replaced with built-in functions.  We have already added some things
> to Emacs in recent years that have been inspired by those libraries,
> and if there is something needed that is still missing, we could
> consider adding that too.
>
> I don't know what "elisp-refs" is or does, but it has the same
> principal author as helpful.el.
>
> So it seems to me that none of this is impossible to resolve, in one
> way or another.
No, of course it is not impossible; I was aware of that when I wrote it, but
still, it means we have to re-work it. But someone else didn't want to have two
different code bases etc. 

What I have learned form this list, is, if I want something to have, I have to
build-it and submit patch, and not even then I am guaranteed to have it in
Emacs :-).

I also haen't seen any responses from Wifred, so I'll just see if I can
implement those things I care most for: lookup docs for autoladed functions
without docs 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, and 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.



  reply	other threads:[~2021-09-10  7:58 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 [this message]
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=AM9PR09MB49775A7AC0A3DB1B0D1A685996D69@AM9PR09MB4977.eurprd09.prod.outlook.com \
    --to=arthur.miller@live.com \
    --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).