From: Drew Adams <drew.adams@oracle.com>
To: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: RE: `declare-function' docu
Date: Thu, 9 Apr 2020 08:47:03 -0700 (PDT) [thread overview]
Message-ID: <ef5d8492-5f9e-4985-bdae-59de094dd297@default> (raw)
In-Reply-To: <87wo6okfis.fsf@oitofelix.com>
> > Similarly, help-fns+.el.
>
> I see you’re the author. Do you plan to
> contribute it to Emacs core or GNU ELPA?
I've offered its code, and that of all my
libraries, several times. A few things from
help-fns+.el have been integrated (e.g.
`describe-keymap' - see Emacs bug #30660),
albeit in a somewhat lesser form. But in
general there's been little to no interest.
From my point of view, I'd much prefer that
vanilla Emacs offer such features, so I'd no
longer need to maintain separate libraries.
In the particular case of adding links from
*Help* to manuals, I think the approaches
being looked at now probably make sense -
they may be performant.
But some aspects of the simple approach to
this taken in help-fns+.el might also help -
such as user choice of whether to find lookup
addresses ahead of time or just when following
links. If the cost of systematically finding
them ahead of time isn't too great, fine.
Besides lookup cost, letting users specify
which manuals to check can be useful - the set
of manuals available differs for different
users/platforms, and which ones to link to
(search) is a question for users.
next prev parent reply other threads:[~2020-04-09 15:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 11:26 Bookmarks in EWW Marcin Borkowski
2020-03-23 14:56 ` Drew Adams
2020-03-25 11:48 ` Marcin Borkowski
2020-03-23 20:41 ` Michael Heerdegen
2020-03-24 14:46 ` Stefan Monnier
2020-03-25 3:05 ` Michael Heerdegen
2020-03-25 3:45 ` `declare-function' docu (was: Re: Bookmarks in EWW) Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-28 17:59 ` `declare-function' docu Bruno Félix Rezende Ribeiro
2020-03-28 18:38 ` Drew Adams
2020-04-09 12:30 ` Bruno Félix Rezende Ribeiro
2020-04-09 15:47 ` Drew Adams [this message]
2020-03-28 21:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-25 14:06 ` Bookmarks in EWW Stefan Monnier
2020-03-26 1:09 ` Michael Heerdegen
2020-03-26 4:07 ` Stefan Monnier
2020-03-27 2:07 ` Michael Heerdegen
2020-03-27 3:44 ` Stefan Monnier
2020-03-28 2:31 ` Michael Heerdegen
2020-03-28 2:55 ` Stefan Monnier
2020-04-19 3:42 ` Michael Heerdegen
2020-04-19 13:18 ` Stefan Monnier
2020-04-20 3:17 ` Michael Heerdegen
2020-04-20 13:24 ` Stefan Monnier
2020-04-21 0:59 ` Michael Heerdegen
2020-04-29 22:53 ` Michael Heerdegen
2020-04-30 1:25 ` Stefan Monnier
2020-04-30 2:08 ` Michael Heerdegen
2020-04-30 3:08 ` Stefan Monnier
2020-04-30 20:09 ` Michael Heerdegen
2020-04-27 2:43 ` Michael Heerdegen
2020-03-27 4:32 ` buffer-localness (was: Re: Bookmarks in EWW) Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-25 21:48 ` Bookmarks in EWW Drew Adams
2020-03-26 2:29 ` Michael Heerdegen
2020-03-26 3:21 ` Drew Adams
2020-03-26 3:53 ` Michael Heerdegen
2020-03-26 14:02 ` Drew Adams
2020-03-26 22:33 ` Michael Heerdegen
2020-03-26 8:41 ` Marcin Borkowski
2020-03-25 11:49 ` Marcin Borkowski
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=ef5d8492-5f9e-4985-bdae-59de094dd297@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=oitofelix@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.
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).