From: "Mingde (Matthew) Zeng" <matthewzmd@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Ergus <spacibba@aol.com>, Naoya Yamashita <conao3@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Include leaf in Emacs distribution
Date: Mon, 12 Oct 2020 16:53:05 -0400 [thread overview]
Message-ID: <871ri3rwsu.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmmJmPJzVf_PeEp_jTzn_Sq_2P3X9tuGSw+9oKQ5yRHfWQ@mail.gmail.com>
> Why would you say that there is no progress? It seems to me that
> exactly the opposite is the case.
>
> See: https://github.com/jwiegley/use-package/issues/282
From what I see the copyright assignment is almost done on the use-package side.
From a pure user's perspective, I very much prefer to use a package named `use-package` instead of `leaf` to manage my emacs packages.
Besides, when choosing a package to use, I personally prefer a matured (in terms of the number of years in development and number of contributors) and a popular (in terms of [m]elpa downloads or Github stars or discussions on forums/reddit) package. These are indications to me that the package is good, useful, and that people trust it. use-package excels in all these places.
Maybe leaf has a better design or has better code quality, I haven't personally read the sourcecode so I have no say here.
Therefore I suggest to wait a bit until the use-package team finalizes the copyright assignment and merge that instead.
Anyways no offence intended toward leaf, it is a cool pakcage and I might try it some day. However I just don't think it would be a really good idea for it to be part of emacs itself.
--
Mingde (Matthew) Zeng
next prev parent reply other threads:[~2020-10-12 20:53 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 [this message]
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=871ri3rwsu.fsf@posteo.net \
--to=matthewzmd@posteo.net \
--cc=conao3@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=spacibba@aol.com \
--cc=stefankangas@gmail.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).