From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] proc(5): fix indentation for net examples
Date: Tue, 31 Dec 2013 00:43:48 -0500 [thread overview]
Message-ID: <201312310043.48914.vapier@gentoo.org> (raw)
In-Reply-To: <52C15897.5060309-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: Text/Plain, Size: 827 bytes --]
On Monday 30 December 2013 06:27:19 Michael Kerrisk (man-pages) wrote:
> On 12/29/13 02:26, Mike Frysinger wrote:
> > Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
>
> I'm not sure what the goal of this change is. What's broken?
> (Note that there is some value, in terms of easy parsing of
> man output, to having only the section headings start in
> column 1.)
i'm not sure what you mean here. having it at col 1 makes scanning the man
page harder imo, and indenting it to match the content that it's part of makes
sense. it's what most every other section does in this man page already.
if you're worried about 80 cols, then this table already widely exceeds that
limit even when placed at col 1. so fixing the indentation doesn't really hurt
that scenario.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-31 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 13:26 [PATCH] proc(5): fix indentation for net examples Mike Frysinger
[not found] ` <1388237204-12791-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2013-12-30 11:27 ` Michael Kerrisk (man-pages)
[not found] ` <52C15897.5060309-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-31 5:43 ` Mike Frysinger [this message]
[not found] ` <201312310043.48914.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-01-01 19:48 ` Michael Kerrisk (man-pages)
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=201312310043.48914.vapier@gentoo.org \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 NNTP newsgroup(s).