From: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>
To: t@fullmeta.me
Cc: zimoun <zimon.toutoune@gmail.com>, help-guix@gnu.org
Subject: Re: Emacs inside container: preserved DISPLAY unavailable etc
Date: Wed, 05 Jan 2022 13:39:53 +0100 [thread overview]
Message-ID: <8735m2uzja.fsf@ruhr-uni-bochum.de> (raw)
In-Reply-To: <87fsq3k6g4.fsf@fastmail.com> (t.'s message of "Tue, 04 Jan 2022 12:29:13 +0000")
Hi,
t@fullmeta.me writes:
> Hi guix.
>
> Straigt out of manual:
>
> --------------------
>
> $ guix shell --container --no-cwd --network emacs-next
> --expose=$HOME/.emacs.d --preserve='^DISPLAY$' -- emacs
>
> No protocol specified
> Display :1 unavailable, simulating -nw
> Please set the environment variable TERM; see 'tset'.
>
> --------------------
I am now using Guix System at
guix 049851d
Repository-URL: https://git.savannah.gnu.org/git/guix.git
Branch: master
Commit: 049851d16ebcf8736161b654291085c223972b7c
and the command fails for me as well:
--8<---------------cut here---------------start------------->8---
$ guix shell --container --no-cwd --network emacs-next --expose=$HOME/.emacs.d --preserve='^DISPLAY$' -- emacs
Authorization required, but no authorization protocol specified
Display :1 unavailable, simulating -nw
Please set the environment variable TERM; see 'tset'.
--8<---------------cut here---------------end--------------->8---
A similar error message happened to me with a chromium example from the
manual as described here:
<https://lists.gnu.org/archive/html/help-guix/2021-12/msg00077.html>
However, Simon wasn't able to reproduce this error with his system as
well. Maybe it is something that happens on Guix system only.
Best,
Daniel
next prev parent reply other threads:[~2022-01-05 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:29 Emacs inside container: preserved DISPLAY unavailable etc t
2022-01-04 17:03 ` zimoun
2022-01-04 17:11 ` Vlad Kozin
2022-01-05 12:39 ` Daniel Meißner [this message]
2022-01-05 13:09 ` t
2022-01-05 14:48 ` Daniel Meißner
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=8735m2uzja.fsf@ruhr-uni-bochum.de \
--to=daniel.meissner-i4k@ruhr-uni-bochum.de \
--cc=help-guix@gnu.org \
--cc=t@fullmeta.me \
--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).