From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary
<jean.christophe.helary@traduction-libre.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: RE: "Emacs Lisp Packages" chapter in the Emacs manual
Date: Mon, 11 May 2020 08:13:13 -0700 (PDT) [thread overview]
Message-ID: <85aacf7d-51cc-420a-a53b-f16f2e497106@default> (raw)
In-Reply-To: <0BBC80E8-7A74-4DB4-8C13-AF2AAFF04B4B@traduction-libre.org>
In my opinion (just one user), a user's notion of
"installing" is one thing. Loading a Lisp file
is another thing. There's some overlap, but the
Elisp, and even the Emacs, manual should at least
present _loading_ Lisp code (byte-compiled or not).
And in that context, `require', `provide', and
"features" are important constructs to document.
There's no wall between Elisp programmers and
Emacs users. Many users are lispers, and many who
are not could be, to everyone's advantage.
I don't think the Emacs doc should tell users not
to use `require'. It can certainly tell them how
convenient it may be to use the package system.
But package installing is not exactly the same
thing as loading Lisp files, and yes, each can be
useful for Emacs users - at least some users.
Just one opinion.
next prev parent reply other threads:[~2020-05-11 15:13 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
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 [this message]
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=85aacf7d-51cc-420a-a53b-f16f2e497106@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.org \
--cc=monnier@iro.umontreal.ca \
/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.