From: Max Techter <mtechter@gmx.de>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Around again, and docs lead role
Date: 13 May 2003 16:14:38 +0200 [thread overview]
Message-ID: <86znlr9bn5.fsf@520000401788.dialin.t-online.de> (raw)
In-Reply-To: <m3u1bzzzdf.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> >>>>> "Max" == Max Techter <mtechter@gmx.de> writes:
>
> Max> Neil Jerram <neil@ossau.uklinux.net> writes:
> Max> snip
> >>
snip
> Max> I am new to guile, new to this list
>
> Max> (though I posted a couple of replies concerning the overall
> Max> structure, and the principle need of tutorials)
>
> First off, apologies for not replying to your earlier detailed email
> yet - I'm a bit busy and taking time to digest it, but it looks like
> just the kind of high-level input that I was hoping someone would
> supply.
snip
Take your time, Neil. I will be engaged in "my
guile analysis" for quite some time.
And there is no chance for me coming up with first
well formed proposals before, say the end of this
month, although I`ll try to supply my comments sooner.
> Max> If you think, that in the current state of discussion, this
> Max> kind of critique could be useful, tell me:
>
> Yes, absolutely!
>
> Max> hacking revised comments into, say the .texi
> Max> source, would not put a too heavy workload on me.
>
snip
On which version exactly should I build?
I produced my printout and info files from:
@set MANUAL_EDITION 1.0
...
...
@title Guile Reference Manual
@subtitle Edition @value{MANUAL_EDITION}, \
for use with Guile @value{VERSION}
# this evaluated to 1.6.2
@subtitle $Id: guile.texi,v 1.2.2.17 2002/09/25 00:12:21 ossau Exp $
Is this OK, or should I switch to a source
from CVS?
> If you have any suggestions for a overall plan of
> how to rectify the problems that you've noted,
> I would love to hear
> them too.
>
Taking the fun of playing the harsh critic,
I would feel obliged to propose better ways,
naturally.
regards
max.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-13 14:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 7:33 Around again, and docs lead role Neil Jerram
2003-04-26 10:19 ` Thamer Al-Harbash
2003-04-27 20:56 ` Neil Jerram
[not found] ` <3E92E1B40021F4D7@pop3.tiscalinet.es>
2003-04-27 21:01 ` Neil Jerram
[not found] ` <3E92E1B4002B0632@pop3.tiscalinet.es>
2003-04-30 22:47 ` Neil Jerram
[not found] ` <3EAFE4EC000D9733@pop1.tiscalinet.es>
2003-05-07 21:06 ` Doc organization (Re: Around again, and docs lead role) Neil Jerram
2003-05-08 16:21 ` Rob Browning
2003-05-08 17:50 ` rm
2003-05-08 22:47 ` Neil Jerram
2003-05-08 21:18 ` Wolfgang Jaehrling
2003-05-08 22:36 ` Neil Jerram
2003-05-09 2:23 ` Rob Browning
2003-05-09 17:46 ` David Van Horn
2003-05-10 11:32 ` Neil Jerram
2003-05-15 16:02 ` Rob Browning
2003-05-15 16:33 ` Paul Jarc
2003-05-08 16:21 ` Max Techter
[not found] ` <3EB9828B00021495@pop1.tiscalinet.es>
2003-05-08 21:12 ` Max Techter
2003-05-27 2:02 ` Max Techter
2003-05-08 22:57 ` Neil Jerram
2003-05-09 12:32 ` Max Techter
2003-05-09 8:15 ` tomas
2003-05-10 12:01 ` Neil Jerram
2003-05-12 11:40 ` tomas
2003-05-12 16:46 ` Around again, and docs lead role Max Techter
2003-05-12 20:25 ` Neil Jerram
2003-05-13 14:14 ` Max Techter [this message]
2003-05-13 19:56 ` Neil Jerram
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=86znlr9bn5.fsf@520000401788.dialin.t-online.de \
--to=mtechter@gmx.de \
--cc=guile-devel@gnu.org \
/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).