From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Can I easily install GNU Emacs 27.1.50 via Guix?
Date: Sat, 19 Dec 2020 11:17:04 +1100 [thread overview]
Message-ID: <87y2hu8xa7.fsf@zancanaro.id.au> (raw)
In-Reply-To: <CAJ3okZ2FLg5djP9Jz3YYvAu16UgQyT=WDtJbmPm4H8bcOdhS+A@mail.gmail.com>
Hi Simon,
On Sat, Dec 19 2020, zimoun wrote:
> I am not sure to agree. The unexpected (by you :-)) behaviour
> at hand is about Emacs and "M-x shell"; and I will not speak "in
> general".
Let's avoid using the word "expected", because that word in this
context can mean different things. I don't "expect" the behaviour
when I think about Guix from a user's perspective, but I do
"expect" the behaviour because I know Guix's implementation
details.
Instead, let's talk about what behaviour we want.
I want to be able to use programs installed by Guix to launch
programs installed by a host distribution's package manager, and
have them function properly. This is not currently the case,
because of the way Guix uses environment variables to set search
paths. In this particular thread we have been talking about Emacs,
but the problem is not limited to Emacs.
Is there an argument for the current behaviour? I'm not aware of
anyone arguing that we want to break programs installed by a host
distribution when we launch them from a Guix installed program.
From my perspective the only argument here is "making it work is
hard, so we haven't done it". This is a good reason for the
current state of things, but it is not a reason to avoid calling
this a bug.
> Well, if you feel it is a bug, please open a bug report
> detailing what is the problem. Personally, I do miss what it is
> and what could be the actionable next step.
Sure. I'll add it to my to-do list.
Carlo
next prev parent reply other threads:[~2020-12-19 0:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 16:46 Can I easily install GNU Emacs 27.1.50 via Guix? Jorge P. de Morais Neto
2020-12-09 20:56 ` Pierre Neidhardt
2020-12-10 12:40 ` zimoun
2020-12-17 22:54 ` Jorge P. de Morais Neto
2020-12-17 22:59 ` Jorge P. de Morais Neto
2020-12-18 2:05 ` zimoun
2020-12-18 4:03 ` Carlo Zancanaro
2020-12-18 9:00 ` zimoun
2020-12-18 9:36 ` Carlo Zancanaro
2020-12-18 10:38 ` zimoun
2020-12-18 11:37 ` Carlo Zancanaro
2020-12-18 13:59 ` zimoun
2020-12-19 0:17 ` Carlo Zancanaro [this message]
2020-12-18 10:44 ` Dr. Arne Babenhauserheide
2020-12-18 12:55 ` Ricardo Wurmus
2020-12-18 14:05 ` zimoun
2020-12-18 15:33 ` Maxim Cournoyer
2020-12-18 15:09 ` Jorge P. de Morais Neto
2020-12-18 23:17 ` Carlo Zancanaro
2020-12-18 9:50 ` Ricardo Wurmus
2020-12-10 12:27 ` 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=87y2hu8xa7.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=help-guix@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.
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).