From: Rical Jasan <ricaljasan@pacific.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: [PATCH 3/3] manual: Add new header and standards annotations.
Date: Mon, 05 Dec 2016 07:59:00 -0000 [thread overview]
Message-ID: <912c288b-d2f2-6ef0-7bd7-ee93b0f734ac@pacific.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1612021351290.32231@digraph.polyomino.org.uk>
On 12/02/2016 05:55 AM, Joseph Myers wrote:
> On Fri, 2 Dec 2016, Rical Jasan wrote:
>
>> Safety: MT-Safe | AS-Unsafe heap | AC-Unsafe mem fd | See Section
>> 1.2.2.1 [POSIX Safety Concepts], page 2.
>> Standards: POSIX.1 (unistd.h), See Section 1.3.4 [Feature Test Macros],
>> page 15.
>> Added in: 2.0
>
> I'm envisaging "Safety" and "Standards" being plain links (in the HTML and
> PDF manuals) to the relevant manual sections, so you don't have the " |
> See Section 1.2.2.1 [POSIX Safety Concepts], page 2." and ", See Section
> 1.3.4 [Feature Test Macros], page 15." text at all. That makes things
> much shorter. (I don't know if you can readily make such plain links from
> Texinfo at present, but I think it looks a lot better that way when you
> have such annotations appearing for every interface in the manual.)
I don't think that's possible using Texinfo. The @*ref-commands allow
some variance in their rendering, but nothing that overrides the entire
rendered string like that, from what I can see.
Rical
next prev parent reply other threads:[~2016-12-05 7:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 6:38 [PATCH 0/3] manual: Header & Standards Cleanup Rical Jasan
2016-11-23 6:38 ` [PATCH 2/3] manual: Convert @tables of variables to @vtables Rical Jasan
2016-11-23 6:38 ` [PATCH 1/3] manual: Refactor header and standards annotations Rical Jasan
2016-11-23 17:31 ` Joseph Myers
2016-11-24 9:34 ` Rical Jasan
2016-11-24 13:17 ` Joseph Myers
2016-11-25 3:44 ` Rical Jasan
2016-11-25 14:25 ` Joseph Myers
2016-11-30 8:58 ` Rical Jasan
2016-11-23 6:38 ` [PATCH 3/3] manual: Add new " Rical Jasan
2016-11-23 17:42 ` Joseph Myers
2016-11-24 10:22 ` Rical Jasan
2016-11-24 13:37 ` Joseph Myers
2016-11-25 5:59 ` Rical Jasan
2016-11-25 14:53 ` Joseph Myers
2016-11-25 15:09 ` Joseph Myers
2016-11-30 10:39 ` Rical Jasan
2016-11-30 10:45 ` Florian Weimer
2016-11-30 12:50 ` Joseph Myers
2016-12-02 11:54 ` Rical Jasan
2016-12-02 13:56 ` Joseph Myers
2016-12-05 7:59 ` Rical Jasan [this message]
2016-11-30 12:38 ` Joseph Myers
2016-12-05 5:33 ` Rical Jasan
2016-12-05 18:22 ` Joseph Myers
2016-12-06 10:57 ` Rical Jasan
2016-12-06 15:59 ` Joseph Myers
2016-12-06 16:36 ` Zack Weinberg
2016-11-25 7:36 ` Rical Jasan
2016-11-25 16:17 ` Joseph Myers
2016-11-30 10:46 ` Rical Jasan
2016-11-30 12:52 ` Joseph Myers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=912c288b-d2f2-6ef0-7bd7-ee93b0f734ac@pacific.net \
--to=ricaljasan@pacific.net \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mtk.manpages@gmail.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).