From: Tomas Volf <~@wolfsden.cz>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
gemmaro <gemmaro.dev@gmail.com>, Andrew Tropin <andrew@trop.in>,
72333@debbugs.gnu.org
Subject: bug#72333: [PATCH] gnu: emacs-transient: Prioritise loading over built-in.
Date: Sat, 17 Aug 2024 11:26:25 +0200 [thread overview]
Message-ID: <ZsBswZLxykKmgsno@ws> (raw)
In-Reply-To: <2b9d6faf689d9f5677387d29ff70f2bfdd1c1e04.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On 2024-07-31 19:10:03 +0200, Liliana Marie Prikler wrote:
> The other (recommended at the moment) would be to use the proper
> transformation to natively compile your emacs packages.
So just to make sure I understand correctly what is the correct work around
here. Let us assume I install emacs and emacs-magit into my home environment.
So until now I have (leaving everything else out) this:
(home-environment
(packages (list emacs emacs-magit <more-here>)))
Assuming I want to follow the recommendation above, I should turn it into
something like this:
(home-environment
(packages (map (package-input-rewriting `((,emacs-minimal . ,emacs)))
(list emacs emacs-magit <more-here>))))
Did I get it right? Are there any downsides to doing this (except compute)?
Have a nice day,
Tomas
Side note: I am surprised how long emacs-yaml takes to build on my ~5.5 GHz
build machine. I compile whole of firefox faster.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-08-17 11:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 12:41 bug#72333: Magit/Transient error message daniel szmulewicz
2024-07-30 22:20 ` Alvin Hsu
2024-07-30 22:50 ` aurtzy
2024-07-31 16:52 ` Richard Sent
2024-07-31 12:04 ` bug#72333: [PATCH] gnu: emacs-transient: Prioritise loading over built-in gemmaro
2024-07-31 17:10 ` Liliana Marie Prikler
2024-08-17 9:26 ` Tomas Volf [this message]
2024-08-17 11:21 ` Liliana Marie Prikler
[not found] ` <87ikvias2d.fsf@gmail.com>
2024-09-02 18:55 ` bug#72333: builtin native-compiled is loaded instead of emacs-packages Simon Tournier
2024-09-02 19:00 ` Simon Tournier
2024-09-02 19:22 ` Liliana Marie Prikler
2024-09-03 15:05 ` Simon Tournier
2024-09-03 14:57 ` bug#72333: [PATCH] gnu: emacs-minimal: Do not native-compile lisp/transient.el Simon Tournier
2024-09-03 16:49 ` Liliana Marie Prikler
2024-09-03 19:47 ` Liliana Marie Prikler
2024-09-03 21:00 ` Simon Tournier
2024-09-14 17:53 ` bug#72333: Magit/Transient error message Rutherther via Bug reports for GNU Guix
2024-09-14 19:12 ` Liliana Marie Prikler
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=ZsBswZLxykKmgsno@ws \
--to=~@wolfsden.cz \
--cc=72333@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=gemmaro.dev@gmail.com \
--cc=liliana.prikler@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.