unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: adriano <randomlooser@riseup.net>
To: Lee Thomas <leet22303be@gmail.com>, 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: Thu, 01 Sep 2022 09:17:10 +0200	[thread overview]
Message-ID: <b59bea93ae79a4dc17cb4b8fa279ab38aade37f3.camel@riseup.net> (raw)
In-Reply-To: <CANYin9WA1DKK6sZdsaFCysyL4Z+R9cgLiPk_OHNGqnGmJehQuA@mail.gmail.com>

Hi Lee,

Il giorno mar, 30/08/2022 alle 11.33 -0700, Lee Thomas ha scritto:
> 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.

I feel you don't need to apologize

With some GNU people, you're never enough

You're not enough smart, you're lazy, you don't want to read the
manual, you don't wanna do you homework, you want to parasiticly
leverage other people's free time

The hypothesis that the problem is in the defect if their communication
is religiously rejected a priori

In fact I run into the same error some years ago and I was berated for
that

You can feel assured it's not your fault

> 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.

That's another religious thing of some communities

repos and issue trackers stuck in the past





  reply	other threads:[~2022-09-01  7:17 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
2022-09-01  7:17                       ` adriano [this message]
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=b59bea93ae79a4dc17cb4b8fa279ab38aade37f3.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=57379@debbugs.gnu.org \
    --cc=david@altosw.be \
    --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).