unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Lee Thomas <leet22303be@gmail.com>
To: David Pirotte <david@altosw.be>
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: Tue, 30 Aug 2022 11:33:32 -0700	[thread overview]
Message-ID: <CANYin9WA1DKK6sZdsaFCysyL4Z+R9cgLiPk_OHNGqnGmJehQuA@mail.gmail.com> (raw)
In-Reply-To: <20220829202346.57027183@aicha>

[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]

So what I meant by "eventually", David, is that the apps were slow to
appear. Without the grafts, now they aren't.

I sincerely apologize for opening a bug on the original issue; it appeared
to be the right thing to do at the time. I am trying to get some apps built
in Guile, and sometimes it is difficult to find information. Plus, I am
dying from cancer, so many times my brain is not as lucid as I need it to
be, so I make social errors. But I do apologize, and I will do better in
the future.

It's not obvious to me how I can close this bug report. I will try to find
out, but if you have a quick response, I would appreciate it.

On Mon, Aug 29, 2022 at 4:23 PM David Pirotte <david@altosw.be> wrote:

> 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: Type: text/html, Size: 3033 bytes --]

  reply	other threads:[~2022-08-30 18:33 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
2022-08-30 18:33                     ` Lee Thomas [this message]
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=CANYin9WA1DKK6sZdsaFCysyL4Z+R9cgLiPk_OHNGqnGmJehQuA@mail.gmail.com \
    --to=leet22303be@gmail.com \
    --cc=57379@debbugs.gnu.org \
    --cc=david@altosw.be \
    --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).