unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 6/8] doc lei: add manpages for new commands
Date: Mon, 29 Mar 2021 03:25:12 +0000	[thread overview]
Message-ID: <YGFImEcWX1mCJJwv@dcvr> (raw)
In-Reply-To: <20210329031117.28516-7-kyle@kyleam.com>

Kyle Meyer <kyle@kyleam.com> wrote:
> +=for comment

> +TODO: The below options are shared with lei-q.  Any good approaches to
> +not repeating the text?

I don't know about natively in POD.  Perhaps just a list of
switches and a pointer to lei-q(1)?

Or maybe we generate some .pod files via cat + sh

  cat lei-blob.pod.in lei-q-common.pod.in >lei-blob.pod

I don't know if depending on cpp or some other widely-installed
preprocessor is worth it.

> +=for comment
> +TODO: Put a table of prefixes somewhere and reference that (at least
> +here and in lei-q)?

Yes, probably.

  reply	other threads:[~2021-03-29  3:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  3:11 [PATCH 0/8] doc: lei manpages, round 4 Kyle Meyer
2021-03-29  3:11 ` [PATCH 1/8] doc lei-q: fix typo in -tt description Kyle Meyer
2021-03-29  3:11 ` [PATCH 2/8] doc lei: note --stdin shortcut in synopses Kyle Meyer
2021-03-29  3:11 ` [PATCH 3/8] doc lei: drop an unnecessary to-do comment Kyle Meyer
2021-03-29  3:11 ` [PATCH 4/8] doc lei: don't render most to-do comments Kyle Meyer
2021-03-29  3:11 ` [PATCH 5/8] doc lei: update manpages with new options Kyle Meyer
2021-03-29  3:11 ` [PATCH 6/8] doc lei: add manpages for new commands Kyle Meyer
2021-03-29  3:25   ` Eric Wong [this message]
2021-03-29  3:35     ` Kyle Meyer
2021-03-29  3:11 ` [PATCH 7/8] doc lei overview: note that lei-init is usually unnecessary Kyle Meyer
2021-03-29  3:11 ` [PATCH 8/8] doc lei overview: better explain routes into local store Kyle Meyer
2021-03-29  3:18 ` [PATCH 0/8] doc: lei manpages, round 4 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=YGFImEcWX1mCJJwv@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. 
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).