unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Naoya Yamashita <conao3@gmail.com>
Cc: johnw@gnu.org, emacs-devel@gnu.org
Subject: Re: Include leaf in Emacs distribution
Date: Mon, 12 Oct 2020 22:13:53 +0000	[thread overview]
Message-ID: <CADwFkmnK6v7qW59m8Ac8Gkh-jQCPxYRsaxcQzXDVYkhL-UOinw@mail.gmail.com> (raw)
In-Reply-To: <20201012.103522.1802478978485184324.conao3@gmail.com>

Naoya Yamashita <conao3@gmail.com> writes:

> From my point of view the syntax of use-package is confusing.
> For example, :when is naturally designed to evaluate a given
> S-expression and is only enabled when non-nil is returned, but
> :disabled is not.  That is, (use-package flymake :disabled t) and
> (use-package flymake :disabled nil) will be converted to nil,
> respectively.  This is unnatural.  Also, :when can be a free
> S-expression, but not :disabled.

I'm not sure I understand.  Are you saying that, in use-package, the
existence of `:disabled' means that the package will not be loaded even
if its value is specified to be nil?

> Other keyword, :mode and :hook specify a cons cell, but :custom
> specifies a list.  This can be confusing for newcomers.

Could you show an example of this?

> Both issue are solved in my leaf.

Do you see any other major benefits of leaf over use-package?  Or the
other way around?

Could you explain why I would want to use one or the other (as a user)?

Could you explain why Emacs would want to include one or the other (as
developers)?

I believe that the answers to the above questions would help improve
everyone's understanding of the issues involved.



  reply	other threads:[~2020-10-12 22:13 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
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 [this message]
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=CADwFkmnK6v7qW59m8Ac8Gkh-jQCPxYRsaxcQzXDVYkhL-UOinw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=conao3@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@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.
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).