From: Ariel Rios <ariel@arcavia.com>
To: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: The ROAD-AHEAD: GNOME 2.0 and guile-gtk
Date: Sun, 03 Sep 2000 20:07:00 -0000 [thread overview]
Message-ID: <1282af210f807d8a8292cac4f0c9ad6e@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <877l8tsg43.fsf@zagadka.ping.de>
> Ah, I remember. I think defsformat.txt is too unfinished to be
> implemented already. I myself would wait with a new .defs format
> until it is clear that it is an advantage to the status quo. That is,
> I'm not against using some other format, but I don't think it is
> important.
>
Ok. So we can put this in the very low priority queue.
I think that making guile-gtk to work and compile with Gtk HEAD
is really more more important.
ariel
next prev parent reply other threads:[~2000-09-03 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000830171310.451.qmail@zagadka.ping.de>
2000-08-30 11:52 ` Marius Vollmer
2000-08-30 12:03 ` thi
2000-08-30 12:46 ` Marius Vollmer
2000-08-30 20:02 ` Ariel Rios
[not found] ` <20000831173532.438.qmail@zagadka.ping.de>
2000-09-03 7:32 ` Marius Vollmer
2000-09-03 20:07 ` Ariel Rios [this message]
2000-08-29 19:33 Ariel Rios
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=1282af210f807d8a8292cac4f0c9ad6e@NO-ID-FOUND.mhonarc.org \
--to=ariel@arcavia.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=mvo@zagadka.ping.de \
/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).