From: Andrew Tropin <andrew@trop.in>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 44555@debbugs.gnu.org
Subject: [bug#44555] [PATCH] gnu: Add emacs-next-use-package
Date: Tue, 10 Nov 2020 20:56:41 +0300 [thread overview]
Message-ID: <CABrWRW0Nwu7hJe-VznLeC8aBZJUzo6XfdFKY8kRtOhok4mYnew@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ1fFBBJdYfqidmMZvZmn_VkgSp9_X4b4wyG=qNKJ0+sLA@mail.gmail.com>
> Maybe I am missing something, but it is not built using 'emacs-next'.
> Why not simply update the package 'emacs-use-package' with a comment
> explaining what you already explained?
It's true, it's built with emacs-minimal and probably the name is
a little confusing in that sense.
The original idea was to just update current emacs-use-package,
but during discussion in #guix leoprikler mentioned that
emacs-use-package works fine for users of Emacs 27 and because
the revision I picked is not a stable tag, but just a fresh
commit of use-package and I do it to make people able to use it
from Emacs 28 it would be logical to create a separate package
and keep stable 2.4 version for other users.
Also, removing diminish from propagated inputs can break
someone's setup.
My original patch was: http://ix.io/2DDt
I think it should be safe to just update emacs-use-package to the
more recent revision. It will work for both 27 and 28 users.
Let me know what you think and what you advise to do next.
--
Best regards,
Andrew Tropin
next prev parent reply other threads:[~2020-11-10 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 15:45 [bug#44555] [PATCH] gnu: Add emacs-next-use-package Andrew Tropin
2020-11-10 16:15 ` Andrew Tropin
2020-11-10 17:16 ` zimoun
2020-11-10 17:56 ` Andrew Tropin [this message]
2020-11-10 19:22 ` Michael Rohleder
2020-11-10 19:36 ` Andrew Tropin
2020-11-10 20:32 ` Michael Rohleder
2020-11-11 7:53 ` Andrew Tropin
2020-11-11 9:35 ` Nicolas Goaziou
2020-11-11 10:02 ` bug#44555: " Nicolas Goaziou
2020-11-11 14:33 ` [bug#44555] " Andrew Tropin
2020-11-10 18:00 ` Leo Prikler
2020-11-11 22:42 ` zimoun
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=CABrWRW0Nwu7hJe-VznLeC8aBZJUzo6XfdFKY8kRtOhok4mYnew@mail.gmail.com \
--to=andrew@trop.in \
--cc=44555@debbugs.gnu.org \
--cc=zimon.toutoune@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 external index
https://git.savannah.gnu.org/cgit/guix.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.