From: Michael Rohleder <mike@rohleder.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 44555@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#44555] [PATCH] gnu: Add emacs-next-use-package
Date: Tue, 10 Nov 2020 20:22:35 +0100 [thread overview]
Message-ID: <87blg5j9tw.fsf@rohleder.de> (raw)
In-Reply-To: <CAJ3okZ1fFBBJdYfqidmMZvZmn_VkgSp9_X4b4wyG=qNKJ0+sLA@mail.gmail.com> (zimoun's message of "Tue, 10 Nov 2020 18:16:35 +0100")
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> 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?
If this package doesn't work with emacs28 as it is, I also think
it is good/ok to bump it to a non release commit.
But why also remove propagated-inputs (diminish)?
I use diminish with emacs28 w/o trouble.
diminish is a very small and clean package/sources (and very funny to
read, *love it*).
Maybe we need to debug this better/harder to find the (real) issue?
Andrew, do you have any error message/debug output for the combination
use-package/diminish with emacs28?
--
Hard work never killed anybody, but why take a chance?
Charlie McCarthy
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-11-10 19:29 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
2020-11-10 19:22 ` Michael Rohleder [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blg5j9tw.fsf@rohleder.de \
--to=mike@rohleder.de \
--cc=44555@debbugs.gnu.org \
--cc=andrew@trop.in \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).