From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 2/3] doc: lei q: split =item aliases onto separate lines
Date: Thu, 29 Apr 2021 01:57:38 +0000 [thread overview]
Message-ID: <20210429015738.GA30172@dcvr> (raw)
In-Reply-To: <87o8dxg97w.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
> Eric Wong writes:
>
> > It makes L</--augment> look nicer without resorting to
> > L<--augment|/-a, --augment> and similarly verbose nastiness.
> >
> > Having each option as a separate =item (with a blank line in
> > between each =item) seems to be the preferred style used within
> > Perl core documentation (I used perlrun.pod as an example),
> > so we'll follow Perl core style, here.
>
> Okay, thanks providing a rationale for using separate lines. I went
> with the single line style based on some combination of a subjective
> visual preference and looking at other manpages (presumably git's).
Yeah, also the existing public-inbox-* manpages were using
commas or slash; probably because I based them on git manpages :x
> > This needs to be done for other manpages, at some point...
>
> I should be able to get to another round of lei doc updates this
> weekend.
Thanks in advance. Also, in response to
https://public-inbox.org/meta/20210227180328.28057-1-kyle@kyleam.com/
w.r.t. lei-convert; I think it's helpful to document
since the WWW interface provides gzipped mboxrd and
IMAP|Maildir are probably the most commonly used.
next prev parent reply other threads:[~2021-04-29 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 4:51 [PATCH 0/3] doc: lei updates around lei-q Eric Wong
2021-04-28 4:51 ` [PATCH 1/3] doc: lei: use /tmp for search results pathnames Eric Wong
2021-04-28 4:51 ` [PATCH 2/3] doc: lei q: split =item aliases onto separate lines Eric Wong
2021-04-29 1:39 ` Kyle Meyer
2021-04-29 1:57 ` Eric Wong [this message]
2021-04-28 4:51 ` [PATCH 3/3] doc: lei q: split --output and --format, note "text" Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210429015738.GA30172@dcvr \
--to=e@80x24.org \
--cc=kyle@kyleam.com \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).