unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Jessica Tallon <tsyesika@tsyesika.se>
To: Lee Thomas <leet22303be@gmail.com>
Cc: 57379@debbugs.gnu.org
Subject: bug#57379: GUI toolkit for Guile 3.0?
Date: Wed, 24 Aug 2022 20:55:46 +0200	[thread overview]
Message-ID: <87edx5qxcd.fsf@tsyesika.se> (raw)
In-Reply-To: <CANYin9U4qWk+tFzLMSmfKLvfMaDqbYPG-UKjZxMJnPN9dq=8PQ@mail.gmail.com>


Lee Thomas <leet22303be@gmail.com> writes:

> Thank you, Jessica! That assurance is all I really needed, but FYI: When I
> type "(use-modules (gi))" into an interactive guile, trying to follow
> https://github.com/spk121/guile-gi/blob/master/examples/cairo.scm , guile
> responds with:
> While compiling expression:
> no code for module (gi)
>
> If you happen to know how to fix that, it'd be fantastic for me. But it
> appears to me to be an issue with guix, so I'm happy to ask over there.

No problem.

I'm using it with guix, for example I can do:

$ guix shell guile guile-gi
$ guile
scheme@(guile-user)> (use-modules (gi))

Could it be that you've installed the guile-gi package with guix, but
it's using a system guile version which isn't set up to look for modules
in the path that guix is putting them in? I'm relatively new to guix so
if the above doesn't work, it's prehaps best asking over with the guix
folks since I'm relatively new to guix too.

-- 
Thanks,
Jessica.





  reply	other threads:[~2022-08-24 18:55 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 [this message]
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
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=87edx5qxcd.fsf@tsyesika.se \
    --to=tsyesika@tsyesika.se \
    --cc=57379@debbugs.gnu.org \
    --cc=leet22303be@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).