From: Ricardo Wurmus <rekado@elephly.net>
To: Ryan Prior <rprior@protonmail.com>
Cc: Giovanni Biscuolo <g@xelera.eu>,
55013@debbugs.gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: bug#55013: Guix-emacs doesn't work
Date: Sat, 25 Mar 2023 23:46:41 +0100 [thread overview]
Message-ID: <87mt40h2hr.fsf@elephly.net> (raw)
In-Reply-To: <FfUtYyKRVadAylIZzIM5yJ8pvQJBf_ka-e_nzVlj303O17Cb-dgp9Vgfllb9Bier6IbdLlo5lYWmtky0h3x4fd7_fOtZ4KS_QfN0X0zyt-4=@protonmail.com>
Ryan Prior <rprior@protonmail.com> writes:
>> this no longer seems to be a problem. Can you please confirm that this
>> issue can be closed now?
>
> I can confirm that the emacs-guix package is still broken.
>
> ## Steps to reproduce
> 1. launch Emacs in a container:
> $ guix shell -C --no-cwd --expose=/gnu --expose=/var --share=/tmp -E DISPLAY emacs emacs-guix -- emacs
> 2. run M-x guix-installed-packages
>
> ### Expected result
> A list of installed packages should appear.
FWIW M-x guix-installed-packages (and all the other stuff) works for me
with my Emacs config. I haven’t tried to reproduce this in a container
yet without my Emacs config, but I’ll try soon.
--
Ricardo
prev parent reply other threads:[~2023-03-25 22:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 23:46 bug#55013: Guix-emacs doesn't work Ryan Prior via Bug reports for GNU Guix
2022-04-21 9:50 ` Giovanni Biscuolo
2022-04-21 14:17 ` Giovanni Biscuolo
2022-04-22 5:27 ` Jan Nieuwenhuizen
2022-04-27 9:13 ` Giovanni Biscuolo
2022-04-27 9:16 ` Giovanni Biscuolo
2023-03-20 19:09 ` Ricardo Wurmus
2023-03-22 6:51 ` Giovanni Biscuolo
2023-03-23 13:32 ` Giovanni Biscuolo
2023-03-23 14:10 ` Giovanni Biscuolo
2023-03-23 14:11 ` Giovanni Biscuolo
2023-03-23 16:31 ` Ricardo Wurmus
2023-03-23 17:06 ` Giovanni Biscuolo
2023-03-25 21:00 ` Ryan Prior via Bug reports for GNU Guix
2023-03-25 22:46 ` Ricardo Wurmus [this message]
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=87mt40h2hr.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=55013@debbugs.gnu.org \
--cc=g@xelera.eu \
--cc=janneke@gnu.org \
--cc=rprior@protonmail.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).