From: Colin Woodbury <colin@fosskers.ca>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Fix minor typos
Date: Fri, 2 Dec 2022 15:09:35 +0900 [thread overview]
Message-ID: <49caae4b-79e2-e80f-af86-04d4437dd14c@fosskers.ca> (raw)
In-Reply-To: <CA+XASoXDVjMjs_WzHB-k-=NnZJwtjpoqMvGt7mkYKdThc3EoKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
> `make html` should do it. The output is in doc/ref/guile.html/index.html
Yup, that does it. For my future doc improvements I'll make sure to
check both sides.
So it seems that both the extra period and the superfluous "see" are
perhaps bugs in Info itself. At least when you open the Guile Guide in
Emacs, are you able to visually confirm what I'm seeing?
Colin
[-- Attachment #2: Type: text/html, Size: 880 bytes --]
next prev parent reply other threads:[~2022-12-02 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 0:39 [PATCH] Fix minor typos Colin Woodbury
2022-12-01 0:17 ` Aleix Conchillo Flaqué
2022-12-01 1:03 ` Colin Woodbury
2022-12-02 5:45 ` Aleix Conchillo Flaqué
2022-12-02 6:09 ` Colin Woodbury [this message]
2022-12-02 17:43 ` Aleix Conchillo Flaqué
2022-12-09 12:31 ` Mikael Djurfeldt
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=49caae4b-79e2-e80f-af86-04d4437dd14c@fosskers.ca \
--to=colin@fosskers.ca \
--cc=aconchillo@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).