From: Marius Vollmer <mvo@zagadka.ping.de>
To: "Greg J. Badros" <gjb@cs.washington.edu>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: gtk-clist-append does not work with shared substrings
Date: Sun, 23 Jan 2000 08:04:00 -0000 [thread overview]
Message-ID: <871z78aifz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <qrrd7qwxrrd.fsf@clavicle.cs.washington.edu>
"Greg J. Badros" <gjb@cs.washington.edu> writes:
> > My current thinking is to convert a composite of mode `in' by copying
> > it, and one of mode `out' or `inout' by modifying it in place. Any
> > thoughts about this?
>
> I've never achieved a deep understanding of the guile-gtk interface
> description stuff, but my naive take on this stuff is that that would be
> sufficient. You definitely don't want to side-effect an in parameter.
Ok, I have now checked in some code for this (also some bug fixes).
Can you give it a try? I didn't really test it.
- Marius
next prev parent reply other threads:[~2000-01-23 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 15:19 Greg J. Badros
2000-01-19 11:10 ` Marius Vollmer
2000-01-19 11:37 ` Greg J. Badros
2000-01-20 22:13 ` Marius Vollmer
2000-01-20 21:22 ` Greg J. Badros
2000-01-23 8:04 ` Marius Vollmer [this message]
2000-01-23 9:26 ` Greg J. Badros
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=871z78aifz.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).