From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: Drew Adams <drew.adams@oracle.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: "Emacs Lisp Packages" chapter in the Emacs manual
Date: Mon, 11 May 2020 23:21:15 -0400 [thread overview]
Message-ID: <jwvsgg54zjn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <920E43F8-B65B-4802-97D3-F64BEBF5E8B8@traduction-libre.org> (Jean-Christophe Helary's message of "Tue, 12 May 2020 09:59:23 +0900")
>> [ The first step is of course to make sure the file is found from
>> `load-path`. ]
>
> Like ask the user to manually do M-x load-library and see the result ?
Traditionally it was done either by telling the user to
put this file somewhere in your `load-path`
or to
(add-to-list 'load-path "/where/ever/you/put/that/file/")
> Well, actually all this started because I wanted to install Drew's
> help-fns+.el and it happens that Drew uses "require".
Then follow Drew's suggestion, since that's how he designed his library.
> So, in case I want to add a similar feature set, would 'require be too much ?
I know nothing about help-fns+ so I can't answer that.
But nowadays libraries should be designed for the case where they're
installed by a tool like package.el and in such a case, the user should
almost never need to `require` the package.
> Would (autoload 'help-fns+) be sufficient ?
`autoload` takes 2 args, the first being a function name and the second
the file in which that function is to be found.
> Keep in mind that this addition is for users who know a minimal subset of
> Emacs lisp (enough to play with their init file), not for authors.
Those users should *never* need to do that: either they install via
something like package.el or they follow steps in the package's
installation instructions.
Stefan
next prev parent reply other threads:[~2020-05-12 3:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 15:02 "Emacs Lisp Packages" chapter in the Emacs manual Jean-Christophe Helary
2020-05-09 15:19 ` Stefan Kangas
2020-05-09 16:47 ` Jean-Christophe Helary
2020-05-10 2:19 ` Jean-Christophe Helary
2020-05-10 14:17 ` Stefan Monnier
2020-05-10 15:05 ` Jean-Christophe Helary
2020-05-10 16:49 ` Stefan Monnier
2020-05-10 17:13 ` Jean-Christophe Helary
2020-05-10 19:28 ` Drew Adams
2020-05-11 1:02 ` Jean-Christophe Helary
2020-05-10 19:35 ` Stefan Monnier
2020-05-11 1:08 ` Jean-Christophe Helary
2020-05-11 1:51 ` Drew Adams
2020-05-11 3:26 ` Stefan Monnier
2020-05-11 4:23 ` Drew Adams
2020-05-11 4:40 ` Stefan Monnier
2020-05-11 6:57 ` Jean-Christophe Helary
2020-05-11 15:09 ` Stefan Monnier
2020-05-11 15:23 ` Drew Adams
2020-05-12 0:59 ` Jean-Christophe Helary
2020-05-12 3:21 ` Stefan Monnier [this message]
2020-05-12 3:50 ` Jean-Christophe Helary
2020-05-12 15:46 ` Drew Adams
2020-05-13 1:43 ` Jean-Christophe Helary
2020-05-13 2:05 ` Drew Adams
2020-05-13 2:27 ` Jean-Christophe Helary
2020-05-13 2:33 ` Drew Adams
2020-05-13 2:46 ` Stefan Monnier
2020-05-13 3:02 ` Jean-Christophe Helary
2020-05-16 10:23 ` Eli Zaretskii
2020-05-16 12:39 ` Jean-Christophe Helary
2020-05-16 14:38 ` Eli Zaretskii
2020-05-16 15:20 ` Jean-Christophe Helary
2020-05-12 15:46 ` Drew Adams
2020-05-11 15:13 ` Drew Adams
2020-05-12 3:18 ` Richard Stallman
2020-05-11 3:23 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvsgg54zjn.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.