public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org
Cc: "Alejandro Colomar" <alx.manpages@gmail.com>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>,
	"Heinz-Jürgen Oertel" <hj.oertel@t-online.de>,
	"Ralph Corderoy" <ralph@inputplus.co.uk>
Subject: [PATCH v4] open_how.2type: ffix
Date: Fri, 29 Jul 2022 17:27:38 +0200	[thread overview]
Message-ID: <20220729152737.27770-1-alx.manpages@gmail.com> (raw)
In-Reply-To: <20220726202643.49890-1-alx.manpages@gmail.com>

Format structures with tbl(1) to improve alignment in
proportional-width font text.

Reported-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Heinz-Jürgen Oertel <hj.oertel@t-online.de>
Cc: Ralph Corderoy <ralph@inputplus.co.uk>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man2type/open_how.2type | 23 ++++++++++++++++++++---
 1 file changed, 20 insertions(+), 3 deletions(-)

diff --git a/man2type/open_how.2type b/man2type/open_how.2type
index 570bc9b22..16f289820 100644
--- a/man2type/open_how.2type
+++ b/man2type/open_how.2type
@@ -13,9 +13,26 @@ Linux kernel headers
 .B #include <linux/openat2.h>
 .PP
 .B struct open_how {
-.BR "    u64  flags;" "    /* " O_ "* flags */"
-.BR "    u64  mode;" "     /* Mode for " O_ { CREAT , TMPFILE "} */"
-.BR "    u64  resolve;" "  /* " RESOLVE_ "* flags */"
+.fi
+.RS 4
+.TS
+lB2 lB2 l1 lX.
+u64	flags;	/*	T{
+.BR O_ *
+flags */
+T}
+u64	mode;	/*	T{
+Mode for
+.BR \%O_ { CREAT , TMPFILE }
+*/
+T}
+u64	resolve;	/*	T{
+.BR RESOLVE_ *
+flags */
+T}
+.TE
+.RE
+.nf
     /* ... */
 .B };
 .fi
-- 
2.36.1


  reply	other threads:[~2022-07-29 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 20:26 [PATCH v3] open_how.2type: ffix Alejandro Colomar
2022-07-29 15:27 ` Alejandro Colomar [this message]
2022-07-29 23:01   ` [PATCH v5 1/2] " Alejandro Colomar
2022-07-29 23:01   ` [PATCH v5 2/2] sockaddr.3type: ffix Alejandro Colomar
2022-07-30  0:15     ` G. Branden Robinson

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=20220729152737.27770-1-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=hj.oertel@t-online.de \
    --cc=linux-man@vger.kernel.org \
    --cc=ralph@inputplus.co.uk \
    /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