From: Arun Isaac <arunisaac@systemreboot.net>
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 16:17:31 +0530 [thread overview]
Message-ID: <877dd0bh6k.fsf@systemreboot.net> (raw)
In-Reply-To: <CADEOadeHG2nnUbC39fJ=T1i3QX+x9LEODdxd7wdecAqdx+pcLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]
next prev parent reply other threads:[~2021-11-22 10:47 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 [this message]
2021-11-22 18:31 ` lloda
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=877dd0bh6k.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--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).