From: Ricardo Wurmus <rekado@elephly.net>
To: Lee Thomas <leet22303be@gmail.com>
Cc: tsyesika@tsyesika.se, 57379@debbugs.gnu.org, david@altosw.be
Subject: bug#57379: GUI toolkit for Guile 3.0?
Date: Fri, 26 Aug 2022 22:35:05 +0200 [thread overview]
Message-ID: <87h71yyc7g.fsf@elephly.net> (raw)
In-Reply-To: <CANYin9UQ5-m0fZ9hi7kdEDSnhO1rjq-02KiWtY2nzVJgdjO=2Q@mail.gmail.com>
Lee Thomas <leet22303be@gmail.com> writes:
> So I assume I haven't fixed the guix environment completely yet, but
> I'm still working on that. The guix toolset is advertised to manage
> all the interdependencies, but I'm not certain that it works in every
> situation. I'll keep trying, though. Thanks again.
Could you please show us how to reproduce this? We would need to see
the Guix command, the code you run, and ideally the output of “guix
describe”.
--
Ricardo
next prev parent reply other threads:[~2022-08-26 20:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 2:35 bug#57379: GUI toolkit for Guile 3.0? Lee Thomas
2022-08-24 12:29 ` Jessica Tallon
2022-08-24 16:05 ` Lee Thomas
2022-08-24 18:55 ` Jessica Tallon
2022-08-24 20:03 ` David Pirotte
2022-08-24 21:49 ` Lee Thomas
2022-08-26 2:27 ` David Pirotte
2022-08-26 20:03 ` Lee Thomas
2022-08-26 20:35 ` Ricardo Wurmus [this message]
2022-08-26 21:11 ` Lee Thomas
2022-08-27 8:30 ` Ricardo Wurmus
2022-08-28 23:04 ` David Pirotte
2022-08-28 22:42 ` David Pirotte
2022-08-29 2:32 ` Lee Thomas
2022-08-29 9:11 ` Ricardo Wurmus
2022-08-29 9:12 ` Ricardo Wurmus
2022-08-29 16:54 ` David Pirotte
2022-08-29 18:22 ` Lee Thomas
2022-08-29 23:23 ` David Pirotte
2022-08-30 18:33 ` Lee Thomas
2022-09-01 7:17 ` adriano
2022-09-03 4:26 ` David Pirotte
2022-08-29 19:55 ` Ricardo Wurmus
2022-08-30 18:24 ` Lee Thomas
2022-09-03 4:15 ` David Pirotte
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h71yyc7g.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=57379@debbugs.gnu.org \
--cc=david@altosw.be \
--cc=leet22303be@gmail.com \
--cc=tsyesika@tsyesika.se \
/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).