From: Doug Evans <dje@sceeck.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: Documentation for Scheme scripting
Date: Tue, 10 Sep 2013 05:29:00 -0000 [thread overview]
Message-ID: <CAEei7h9s+sqRtL9BWC=zWyi0Tb4Uj-w5M9_HcWzGs=P49FjAcg@mail.gmail.com> (raw)
In-Reply-To: <87k3iqj5fk.fsf@fleche.redhat.com>
On Mon, Sep 9, 2013 at 10:00 AM, Tom Tromey <tromey@redhat.com> wrote:
>[...] I think it is
> unreasonable to require all Python changes to come with Scheme patches
> as well.
No disagreement there.
> I think the Scheme docs have to just be a whole separate section
> spelling everything out in Scheme terms.
>
> Though I would like to say now that this isn't really Scheme we're
> talking about, but Guile. There are differences. I think it would be
> best to be explicit about that in the docs.
How far do you think Guile vs Scheme should be pushed?
Should the command to invoke a Scheme command be named "guile" instead
of "scheme"?
Should the gdb subdirectory be gdb/guile over gdb/scheme?
next prev parent reply other threads:[~2013-09-10 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 21:12 Doug Evans
2013-09-09 2:47 ` Eli Zaretskii
2013-09-09 17:00 ` Tom Tromey
2013-09-09 17:13 ` Eli Zaretskii
2013-09-10 5:30 ` Doug Evans
2013-09-10 5:29 ` Doug Evans [this message]
2013-09-10 15:25 ` Eli Zaretskii
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='CAEei7h9s+sqRtL9BWC=zWyi0Tb4Uj-w5M9_HcWzGs=P49FjAcg@mail.gmail.com' \
--to=dje@sceeck.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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