From: zimoun <zimon.toutoune@gmail.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix@gnu.org
Subject: Re: Can I easily install GNU Emacs 27.1.50 via Guix?
Date: Fri, 18 Dec 2020 10:00:33 +0100 [thread overview]
Message-ID: <86h7ojmqtq.fsf@gmail.com> (raw)
In-Reply-To: <875z4z4v6s.fsf@zancanaro.id.au>
Hi,
On Fri, 18 Dec 2020 at 15:03, Carlo Zancanaro <carlo@zancanaro.id.au> wrote:
> On Fri, Dec 18 2020, zimoun wrote:
>>> When I launch Debian's Evince from Guix's emacs-maint, Evince
>>> cannot find my local printer. Look at the messages when I open
>>> Evince in an Emacs shell and open Evince's print dialog:
>>
>> Well, it seems expected, isn’t it? ...
>
> I don't think "expected" is the right way to put this. I think
> "explainable" is more accurate. I think it's reasonable to expect
> that opening Debian's Evince from within Emacs would be able to
> find the printers. The fact that it cannot is a bug introduced by
> Guix's use of environment variables.
Maybe I miss something and I have not dove into all the details so I
could be totally wrong. However, from my understanding, A is built
against the shared library C1, and B is built against the shared library
C2, and nothing says that C1 and C2 are compatible. If you run A inside
B, then C2 is used for both A and B, and A fails because it expects C1
and finds instead C2. I miss why it is considered as a bug. Aside the
fact that A and C1 are system-wide so without any control on how it is
built.
From my understanding, it is a bug if A built against C2 run inside B
built too against C2 does not work; which correspond to:
guix environment --pure --ad-hoc emacs evince
emacs -q -f shell
and type “evince”.
Then I do not have any error when I open the print dialog; but I have no
setup for CUPS on my machine though.
And it appears to me also a bug if:
guix environment --pure --ad-hoc emacs-no-x
emacs -q -f shell
and type “/usr/bin/evince” where the print dialog fails. On my machine,
it is not the case; but I have no setup for CUPS on my machine though.
Otherwise, from my point of view, failure should happen and I miss why
it should be considered as a bug, but as I said, I should probably miss
something and be wrong.
> I run into a similar problem where my window manager (awesomewm)
> sets LD_LIBRARY_PATH, which then propagates to everything I run
> from my session. It's quite a pain. I thought there was an open
> issue for this, but I can't seem to find it at the moment.
On foreign distro or Guix System?
All the best,
simon
next prev parent reply other threads:[~2020-12-18 9:01 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 [this message]
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
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=86h7ojmqtq.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=carlo@zancanaro.id.au \
--cc=help-guix@gnu.org \
/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).