From: Eric Wong <e@80x24.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] public-inbox-v2-format(5): fix formatting
Date: Mon, 7 Oct 2019 20:52:04 +0000 [thread overview]
Message-ID: <20191007205204.GA28120@dcvr> (raw)
In-Reply-To: <20191007202725.16802-1-hi@alyssa.is>
Alyssa Ross <hi@alyssa.is> wrote:
> This was being rendered as a paragraph, so line breaks weren't
> preserved and it was unreadable in man.
Thanks for noticing that, it's obvious I never really looked at
the result :x (and I'm writing a new .pod right now, too)
> diff --git a/Documentation/public-inbox-v2-format.pod b/Documentation/public-inbox-v2-format.pod
> index 28d3550..58e6b6d 100644
> --- a/Documentation/public-inbox-v2-format.pod
> +++ b/Documentation/public-inbox-v2-format.pod
> @@ -24,13 +24,13 @@ $EPOCH - Integer starting with 0 based on time
> $SCHEMA_VERSION - PublicInbox::Search::SCHEMA_VERSION used by Xapian
> $PART - Integer (0..NPROCESSORS)
Looks like the lines preceding this patch need to be indented to
preserve newlines, too.
> -foo/ # assuming "foo" is the name of the list
> -- inbox.lock # lock file (flock) to protect global state
> -- git/$EPOCH.git # normal git repositories
> -- all.git # empty git repo, alternates to git/$EPOCH.git
> -- xap$SCHEMA_VERSION/$SHARD # per-shard Xapian DB
> -- xap$SCHEMA_VERSION/over.sqlite3 # OVER-view DB for NNTP and threading
> -- msgmap.sqlite3 # same the v1 msgmap
> + foo/ # assuming "foo" is the name of the list
> + - inbox.lock # lock file (flock) to protect global state
> + - git/$EPOCH.git # normal git repositories
> + - all.git # empty git repo, alternates to git/$EPOCH.git
> + - xap$SCHEMA_VERSION/$SHARD # per-shard Xapian DB
> + - xap$SCHEMA_VERSION/over.sqlite3 # OVER-view DB for NNTP and threading
> + - msgmap.sqlite3 # same the v1 msgmap
I noticed both the original and post-patch manpage exceeds the
limits of an 80-column terminal. I think it's worth it to
reflow and perhaps reword to ensure folks who are limited to 80
columns can viwe (but I can take care of it, too, if you're busy)
Even fitting 80 columns on my screen is a challenge with the
giant fonts I need to workaround poor eyesight :<
next prev parent reply other threads:[~2019-10-07 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 20:27 [PATCH] public-inbox-v2-format(5): fix formatting Alyssa Ross
2019-10-07 20:52 ` Eric Wong [this message]
2019-10-07 21:13 ` Alyssa Ross
2019-10-15 20:11 ` [PATCH 2/1] doc: v2-format: get man output under 80 cols 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=20191007205204.GA28120@dcvr \
--to=e@80x24.org \
--cc=hi@alyssa.is \
--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).