From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ben Hancock <lists@benghancock.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Local postgres manual
Date: Fri, 03 Nov 2023 15:58:05 -0400
Message-ID: <3333527.1699041485@sss.pgh.pa.us> (raw)
In-Reply-To: <2ad88fa8-e0c7-b678-232b-30af59448133@benghancock.com>
References: <c1e0067d-ab06-2bde-2ea9-9ace478a1191@benghancock.com>
<ZUT2sbhj0g_LnVdu@momjian.us>
<2ad88fa8-e0c7-b678-232b-30af59448133@benghancock.com>
Ben Hancock <lists@benghancock.com> writes:
> I will say that, as the manual is quite large, a local GNU Info version
> would be great to be able to traverse different sections, etc, more
> easily. If that doesn't exist already, I wonder if a tool like `pandoc`
> could be employed to generate that.
That's exactly what the postgres.txt file Bruce mentioned is.
# single-page text
postgres.txt: postgres.html
$(PANDOC) -t plain -o $@ $<
These variant doc forms aren't terribly well (or at all) documented,
but the doc/src/sgml Makefile knows how to create a number of them.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, lists@benghancock.com
Subject: Re: Local postgres manual
In-Reply-To: <3333527.1699041485@sss.pgh.pa.us>
References: <c1e0067d-ab06-2bde-2ea9-9ace478a1191@benghancock.com> <ZUT2sbhj0g_LnVdu@momjian.us> <2ad88fa8-e0c7-b678-232b-30af59448133@benghancock.com> <3333527.1699041485@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox