From: David Pirotte <david@altosw.be>
To: Lee Thomas <leet22303be@gmail.com>
Cc: Jessica Tallon <tsyesika@tsyesika.se>,
Ricardo Wurmus <rekado@elephly.net>,
57379@debbugs.gnu.org
Subject: bug#57379: GUI toolkit for Guile 3.0?
Date: Mon, 29 Aug 2022 20:23:46 -0300 [thread overview]
Message-ID: <20220829202346.57027183@aicha> (raw)
In-Reply-To: <CANYin9Vp6cea4zGCAj99Eq=jGJa2JfH9D2ZCx_ZN4C2Ro6XOVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
Hi Lee,
> Thank you again, David. I followed your installation instructions,
> and with a few warnings, your hello-world example (eventually) ran.
Great. What do you mean by '(eventually) ran'? Everything works fine,
'out of the box' and with no warnings, on debian ...
> can submit what I saw to the bug-g-golf@gnu.org address.
No, please don't report warnings on bug-g-golf@gnu.org, rather, use the
guile-user ML, prefixing all g-golf related messages using 'G-Golf - ',
as proposed here https://www.gnu.org/software/g-golf/contact.html
> I also got clipboard.scm to run, with one error.
afaict, all examples should work fine, with no warning(s) and no
error(s)
Please post a (separate) guile-user ML email with the error, as there is
no error nor any warning here (debian testing), I'd need to see ...
> I think for Jessica's and Ricardo's sakes, and because it's the right
> thing to do, we can close bug #57379 and carry on elsewhere.
You should definitely close bug#57379, which shouldn't have been opened
in the first place: it was not a guile nor a g-golf bug in the first
place ...
I invite you to report the warning(s) and bug(s) in separate
guile-user ML email(s) - start a new thread for every diff subject,
let's not mix things and examples ... also, why don't you join us on
irc.libera.chat as well, both #guile and #guix (which I follow but I do
not participate, unless g-golf, guile-lib ... related, only wrt those
packages I am involved in ...)
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-29 23:23 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
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 [this message]
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=20220829202346.57027183@aicha \
--to=david@altosw.be \
--cc=57379@debbugs.gnu.org \
--cc=leet22303be@gmail.com \
--cc=rekado@elephly.net \
--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).