From: Maxime Devos <maximedevos@telenet.be>
To: Simon Tournier <zimon.toutoune@gmail.com>, 67292@debbugs.gnu.org
Subject: bug#67292: emacs / emacs-transient collisions and bundling
Date: Mon, 20 Nov 2023 13:42:05 +0100 [thread overview]
Message-ID: <e382f178-e6b9-a4da-7f6e-919778deaf37@telenet.be> (raw)
In-Reply-To: <d7740e36-6c7d-35bf-64c1-2218c3e01198@telenet.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 790 bytes --]
>>> Bug 2: no collision handling.
>>
>> This is a bug, IMHO. Indeed, if an user prefers another version of
>> builtin modes or packages, they should not collide with the builtin
>> ones. Well, they do not collide when using “guix shell”:
>>
>> guix shell -C emacs emacs-transient -E TERM -- emacs -q
>>
>> Therefore, maybe the issue comes from some specific code from “guix
>> home”. Hum, I do not know.
>
> They do, in fact, collide -- as I mentioned in the e-mail you replied to:
>
>> [...] because "guix shell" (and likewise for "environment") suppresses
>> collision error messages:
>>
>> $ guix shell emacs emacs-transient
>>
>> (see: https://issues.guix.gnu.org/54350).
More info: (guix profiles) does not seem to handle this anywhere.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2023-11-20 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 22:44 bug#67292: emacs / emacs-transient collisions and bundling Maxime Devos
2023-11-20 10:22 ` Simon Tournier
2023-11-20 12:39 ` Maxime Devos
2023-11-20 12:42 ` Maxime Devos [this message]
2023-11-20 13:46 ` Simon Tournier
2023-11-21 18:01 ` Maxime Devos
2023-11-22 20:53 ` Simon Tournier
2023-11-28 1:47 ` Maxime Devos
2023-11-28 9:45 ` Simon Tournier
2023-11-28 11:15 ` Mekeor Melire
2023-11-23 14:17 ` Mekeor Melire
2023-11-28 0:58 ` Maxime Devos
2023-11-28 11:12 ` Mekeor Melire
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=e382f178-e6b9-a4da-7f6e-919778deaf37@telenet.be \
--to=maximedevos@telenet.be \
--cc=67292@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 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).