From: lloda <lloda@sarc.name>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: how to submit error in documentation
Date: Mon, 22 Nov 2021 19:31:51 +0100 [thread overview]
Message-ID: <304DCEC3-96C9-43DB-883B-B97ED174EC5F@sarc.name> (raw)
In-Reply-To: <877dd0bh6k.fsf@systemreboot.net>
Hi,
I just fixed this in git, thanks for the report.
But yeah, if you have more, like Arun says, ideally send it to bug-guile. That way if no one gets to it immediately at least it will be tracked.
Regards
Daniel
> On 22 Nov 2021, at 11:47, Arun Isaac <arunisaac@systemreboot.net> wrote:
>
>
> Hi Damien,
>
>> for example here:
>> https://www.gnu.org/software/guile/manual/html_node/while-do.html
>>
>> the result of :
>>
>> (do ((i 1 (1+ i))
>> (p 3 (* 3 p)))
>> ((> i 4)
>> p)
>> (format #t "3**~s is ~s\n" i p))
>>
>> is not 789
>>
>> but 243:
>
> Good catch!
>
>> what it is the good place or way to submit or correct errors and typos in
>> guile documentation?
>
> You can send a patch (created using `git format-patch') to
> bug-guile@gnu.org.
>
> Regards,
> Arun
next prev parent reply other threads:[~2021-11-22 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 9:16 how to submit error in documentation Damien Mattei
2021-11-22 10:47 ` Arun Isaac
2021-11-22 18:31 ` lloda [this message]
2021-11-22 18:40 ` Damien Mattei
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=304DCEC3-96C9-43DB-883B-B97ED174EC5F@sarc.name \
--to=lloda@sarc.name \
--cc=damien.mattei@gmail.com \
--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).