| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Adding xreflable |
| Date: | 2020-06-04 17:14:17 |
| Message-ID: | 1a9904ee-b5f5-768b-25f4-5be52ee6ce7e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 2020-06-02 18:07, Bruce Momjian wrote:
> I can adjust things, but what logic are we following? Before my patch,
> sepgsql had an xreflabel, and vacuumlo did not. I would like to have a
> documented policy of where we should have xreflabels, and where not, and
> I can then adjust things to match. I don't mind using <link> but it is
> confusing to be able to reference xreflabels in some places and be
> required to use link in others.
One reason for that difference specifically is that vacuumlo is refentry
which can generate its own link text like "vacuumlo(1)", and sepgsql is
a sect1, which by default creates text like "Section 23.2", which
perhaps someone wanted to override.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-06-05 08:22:07 | pg_basebackup in tar format with -Xs |
| Previous Message | Peter Eisentraut | 2020-06-04 17:11:41 | Re: Adding xreflable |