unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Jorge P. de Morais Neto" <jorge+list@disr.it>
Cc: guix-devel@gnu.org
Subject: Re: Why do Emacs packages still pull emacs-transient?
Date: Wed, 06 Jul 2022 09:35:28 -0400	[thread overview]
Message-ID: <87iloa2wkf.fsf@gmail.com> (raw)
In-Reply-To: <87sfnhalvo.fsf@disr.it> (Jorge P. de Morais Neto's message of "Sun, 03 Jul 2022 19:10:03 -0300")

Hi Jorge,

"Jorge P. de Morais Neto" <jorge+list@disr.it> writes:

> Hi.  To begin, thank you for your work on GNU!
>
> I use Guix package manager (manually installed) atop Debian bullseye.
> My Emacs is from Guix package emacs-next with a package transformation
> option to pull from current Git master.  When I tried to use the new
> emoji commands on the "C-x 8e" prefix, I was getting an error message
> (sorry for not having written it down) mentioning transient.  I solved
> it by modifying Guix recipes to not pull emacs-transient as propagated
> input of some Emacs packages I installed via Guix.
>
> So, why do many Emacs packages still pull emacs-transient, when Guix has
> Emacs version 28.1, which has Transient built-in?  This redundancy
> wastes (a little bit of) bandwidth, install time and disk space, and,
> worse, causes errors.

I guess it's simply an oversight.  Could you try to removing it from the
affected packages and see if they still byte compile and run happily?
If they do, a patch would be welcome.

Thanks!

Maxim


  parent reply	other threads:[~2022-07-06 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 22:10 Why do Emacs packages still pull emacs-transient? Jorge P. de Morais Neto
2022-07-04 12:41 ` zimoun
2022-07-06 12:47   ` Jorge P. de Morais Neto
2022-07-06 13:35 ` Maxim Cournoyer [this message]
2022-07-08 12:56   ` Jorge P. de Morais Neto

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=87iloa2wkf.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jorge+list@disr.it \
    /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).