From: Ariel Rios <jarios@usa.net>
To: Greg Badros <gjb@cs.washington.edu>, Ariel Rios <jarios@usa.net>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: [Re: [Re: Using guile-gtk with new guile 1.3.4]]
Date: Sun, 26 Sep 1999 11:47:00 -0000 [thread overview]
Message-ID: <19990926184843.2931.qmail@nwcst021.netaddress.usa.net> (raw)
Greg Badros <gjb@cs.washington.edu> wrote:
> I agree, but the bug is pretty pervasive... I'm really surprised that
> others haven't run into it yet.
Can you explain to me the bug?
> Avoiding people having to use CVS guile-gtk is *exactly* why we need to
> wait for the bug fix... otherwise I'll have to get people to use
> post-guile-gtk-0.17 out of CVS to have the bug fix.
But we can also have the bug fix in guile-gtk 0.18 =)
Ariel
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
reply other threads:[~1999-09-26 11:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990926184843.2931.qmail@nwcst021.netaddress.usa.net \
--to=jarios@usa.net \
--cc=gjb@cs.washington.edu \
--cc=guile-gtk@sourceware.cygnus.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).