From: Naoya Yamashita <conao3@gmail.com>
To: rms@gnu.org
Cc: eliz@gnu.org, spacibba@aol.com, emacs-devel@gnu.org
Subject: Re: Include leaf in Emacs distribution
Date: Sun, 11 Oct 2020 17:39:35 +0900 (JST) [thread overview]
Message-ID: <20201011.173935.1738419864467193536.conao3@gmail.com> (raw)
In-Reply-To: <E1kRTqd-00078k-8Y@fencepost.gnu.org>
> > FWIW, I find the name of the package, 'leaf', to be unintuitive. Can
> > we please have a better name, like load-package or activate-package or
> > something like that?
>
> Hear, hear!
A leaf represents a set of settings, not necessarily a package
unit. It look at Emacs settings from a different perspective
from use-package's one as a package philosophy.
As the name implies, use-package expresses a package's
configuration in a single use-package macro. So jweigley who is
the use-package author expects one use-package per package, and
they are all written at the top level with no nesting[1]. And
the keywordless use-package will be converted into a `require`
statement using the first argument.
On the other hand, what the leaf manages is a "block of
configuration". Therefore, leaf without the keyword will be
converted to `prog1`. And because it is a configuration block, a
package configuration can be described in multiple leaves instead
of one leaf. Also, while jweigley expects use-package to be
written without nesting, I expect the leaf statements to be
nested according to the context.
What I envisioned when I started the project was a picture of
each individual setting mass, each leaf, doing its part to make
up a whole, a big tree. Because I envisioned multiple leaves for
a single package in this way, I came up with the package name
"leaf" instead of "package".
[1]: https://github.com/jwiegley/use-package/issues/453#issuecomment-347750736
next prev parent reply other threads:[~2020-10-11 8:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:37 Include leaf in Emacs distribution Naoya Yamashita
2020-10-08 9:00 ` Ergus
2020-10-08 9:22 ` Naoya Yamashita
2020-10-10 10:11 ` Eli Zaretskii
2020-10-11 5:24 ` Richard Stallman
2020-10-11 8:39 ` Naoya Yamashita [this message]
2020-10-11 9:52 ` Thibaut Verron
2020-10-11 16:50 ` Naoya Yamashita
2020-10-11 17:12 ` Thibaut Verron
2020-10-12 2:10 ` Naoya Yamashita
2020-10-12 20:23 ` Ergus via Emacs development discussions.
2020-10-11 17:02 ` Stefan Kangas
2020-10-11 16:51 ` Stefan Kangas
2020-10-12 20:53 ` Mingde (Matthew) Zeng
2020-10-11 17:22 ` Stefan Kangas
2020-10-12 1:35 ` Naoya Yamashita
2020-10-12 22:13 ` Stefan Kangas
2020-10-12 22:19 ` Qiantan Hong
2020-10-12 22:39 ` Caio Henrique
2020-10-13 13:23 ` Stefan Monnier
2020-10-13 14:14 ` Thibaut Verron
2020-10-13 14:29 ` Stefan Monnier
2020-10-13 15:29 ` Thibaut Verron
2020-10-18 9:32 ` Phil Sainty
2020-10-13 15:25 ` Caio Henrique
2020-10-23 2:37 ` Naoya Yamashita
2020-10-23 3:41 ` John Wiegley
2020-10-23 14:33 ` Stefan Monnier
2020-10-23 15:53 ` Naoya Yamashita
2020-10-23 16:46 ` Warnings in init files (was: Include leaf in Emacs distribution) Stefan Monnier
2020-10-23 18:11 ` Include leaf in Emacs distribution T.V Raman
2020-10-23 18:41 ` Stefan Kangas
2020-10-23 20:04 ` John Wiegley
2020-11-16 5:29 ` Naoya Yamashita
2020-11-17 0:39 ` John Wiegley
2020-11-20 11:04 ` Naoya Yamashita
2020-11-20 11:29 ` Pankaj Jangid
2020-11-20 15:44 ` T.V Raman
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=20201011.173935.1738419864467193536.conao3@gmail.com \
--to=conao3@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=spacibba@aol.com \
/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).