From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Synacek <jsynacek@redhat.com>
Cc: 41352-done@debbugs.gnu.org
Subject: bug#41352: incomprehensible paragraph in info pages
Date: Wed, 27 May 2020 22:50:56 +0200 [thread overview]
Message-ID: <87o8q9hzkf.fsf@gnu.org> (raw)
In-Reply-To: <m6feeri7ss4.fsf@jsynacek-ntb.brq.redhat.com> (Jan Synacek's message of "Sun, 17 May 2020 12:35:55 +0200")
Jan Synacek <jsynacek@redhat.com> skribis:
> In guile-3.0.2 manual, section 6.9.3 Compiled Procedures, there is:
>
> Compiled procedures, also known as “programs”, respond all procedures
> that operate on procedures. In addition, there are a few more accessors
> for low-level details on programs.
>
> The first compound sentence doesn't make much sense. There seems to be a
> word missing, but it's really hard to tell.
Fixed like this:
https://git.savannah.gnu.org/cgit/guile.git/commit/?id=e7ad7eb90b02e9a576e6281cce46494d8b62996c
Ludo’.
prev parent reply other threads:[~2020-05-27 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 10:35 bug#41352: incomprehensible paragraph in info pages Jan Synacek
2020-05-27 20:50 ` Ludovic Courtès [this message]
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=87o8q9hzkf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41352-done@debbugs.gnu.org \
--cc=jsynacek@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).