Hello Bjarni,
On 1/29/19 4:07 AM, Bjarni Ingi Gislason wrote:
> Use a single-font-style macro (".B", ".I") for a single argument.
>
> The output from "nroff" and "groff" is unchanged, except for
>
> 1) '.' is separated from a word to get a roman style.
Applied manually.
> 2) ',' is added in a long list.
If this list was running text, then yes, I'd add commas. But
in this case, It looks out of place to me.
Thanks,
Michael
> Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
> ---
> man4/fuse.4 | 90 ++++++++++++++++++++++++++---------------------------
> 1 file changed, 45 insertions(+), 45 deletions(-)
>
> diff --git a/man4/fuse.4 b/man4/fuse.4
> index d06a86f80..78be7a9d3 100644
> --- a/man4/fuse.4
> +++ b/man4/fuse.4
> @@ -116,7 +116,7 @@ so not all messages are documented.
> For each message, first the struct sent by the kernel is given,
> followed by a description of the semantics of the message.
> .TP
> -.BR FUSE_INIT
> +.B FUSE_INIT
> .IP
> .in +4n
> .EX
> @@ -176,7 +176,7 @@ The negotiated minor version is considered to be the minimum
> of the minor versions provided by the daemon and the kernel and
> both parties should use the protocol corresponding to said minor version.
> .TP
> -.BR FUSE_GETATTR
> +.B FUSE_GETATTR
> .IP
> .in +4n
> .EX
> @@ -195,11 +195,11 @@ by
> and similar operations for the given file system object.
> The object for which the attributes should be computed is indicated
> either by
> -.IR header\->nodeid
> +.I header\->nodeid
> or, if the
> -.IR FUSE_GETATTR_FH
> +.I FUSE_GETATTR_FH
> flag is set, by the file handle
> -.IR fh.
> +.IR fh .
> The latter case of operation is analogous to
> .BR fstat (2).
> .IP
> @@ -243,7 +243,7 @@ struct fuse_attr_out {
> .in
> .IP
> .TP
> -.BR FUSE_ACCESS
> +.B FUSE_ACCESS
> .IP
> .in +4n
> .EX
> @@ -307,13 +307,13 @@ field is a bit mask of any number of the flags
> that indicate properties of this file handle to the kernel:
> .RS 7
> .TP 18
> -.BR FOPEN_DIRECT_IO
> +.B FOPEN_DIRECT_IO
> Bypass page cache for this open file.
> .TP
> -.BR FOPEN_KEEP_CACHE
> +.B FOPEN_KEEP_CACHE
> Don't invalidate the data cache on open.
> .TP
> -.BR FOPEN_NONSEEKABLE
> +.B FOPEN_NONSEEKABLE
> The file is not seekable.
> .RE
> .TP
> @@ -340,7 +340,7 @@ bytes of the file or directory, starting at
> .IR offset .
> The bytes should be returned directly following the usual reply header.
> .TP
> -.BR FUSE_INTERRUPT
> +.B FUSE_INTERRUPT
> .in +4n
> .EX
> struct fuse_interrupt_in {
> @@ -363,7 +363,7 @@ request will be issued for a given operation.
> After issuing said operation,
> the kernel will wait uninterruptibly for completion of the indicated request.
> .TP
> -.BR FUSE_LOOKUP
> +.B FUSE_LOOKUP
> Directly following the header is a filename to be looked up in the directory
> indicated by
> .IR header\->nodeid .
> @@ -394,7 +394,7 @@ The interpretation of timeouts and
> is as for
> .BR FUSE_GETATTR .
> .TP
> -.BR FUSE_FLUSH
> +.B FUSE_FLUSH
> .in +4n
> .EX
> struct fuse_flush_in {
> @@ -425,9 +425,9 @@ struct fuse_release_in {
> .in
> .IP
> These are the converse of
> -.BR FUSE_OPEN
> +.B FUSE_OPEN
> and
> -.BR FUSE_OPENDIR
> +.B FUSE_OPENDIR
> respectively.
> The daemon may now free any resources associated with the
> file handle
> @@ -437,7 +437,7 @@ There is no reply data associated with this request,
> but a reply still needs to be issued once the request has
> been completely processed.
> .TP
> -.BR FUSE_STATFS
> +.B FUSE_STATFS
> This operation implements
> .BR statfs (2)
> for this filesystem.
> @@ -523,36 +523,36 @@ The following messages are not yet documented in this manual page:
> .\" FIXME: Document the following.
> .in +4n
> .EX
> -.BR FUSE_BATCH_FORGET
> -.BR FUSE_BMAP
> -.BR FUSE_CREATE
> -.BR FUSE_DESTROY
> -.BR FUSE_FALLOCATE
> -.BR FUSE_FORGET
> -.BR FUSE_FSYNC
> -.BR FUSE_FSYNCDIR
> -.BR FUSE_GETLK
> -.BR FUSE_GETXATTR
> -.BR FUSE_IOCTL
> -.BR FUSE_LINK
> -.BR FUSE_LISTXATTR
> -.BR FUSE_LSEEK
> -.BR FUSE_MKDIR
> -.BR FUSE_MKNOD
> -.BR FUSE_NOTIFY_REPLY
> -.BR FUSE_POLL
> -.BR FUSE_READDIRPLUS
> -.BR FUSE_READLINK
> -.BR FUSE_REMOVEXATTR
> -.BR FUSE_RENAME
> -.BR FUSE_RENAME2
> -.BR FUSE_RMDIR
> -.BR FUSE_SETATTR
> -.BR FUSE_SETLK
> -.BR FUSE_SETLKW
> -.BR FUSE_SYMLINK
> -.BR FUSE_UNLINK
> -.BR FUSE_WRITE
> +.BR FUSE_BATCH_FORGET ,
> +.BR FUSE_BMAP ,
> +.BR FUSE_CREATE ,
> +.BR FUSE_DESTROY ,
> +.BR FUSE_FALLOCATE ,
> +.BR FUSE_FORGET ,
> +.BR FUSE_FSYNC ,
> +.BR FUSE_FSYNCDIR ,
> +.BR FUSE_GETLK ,
> +.BR FUSE_GETXATTR ,
> +.BR FUSE_IOCTL ,
> +.BR FUSE_LINK ,
> +.BR FUSE_LISTXATTR ,
> +.BR FUSE_LSEEK ,
> +.BR FUSE_MKDIR ,
> +.BR FUSE_MKNOD ,
> +.BR FUSE_NOTIFY_REPLY ,
> +.BR FUSE_POLL ,
> +.BR FUSE_READDIRPLUS ,
> +.BR FUSE_READLINK ,
> +.BR FUSE_REMOVEXATTR ,
> +.BR FUSE_RENAME ,
> +.BR FUSE_RENAME2 ,
> +.BR FUSE_RMDIR ,
> +.BR FUSE_SETATTR ,
> +.BR FUSE_SETLK ,
> +.BR FUSE_SETLKW ,
> +.BR FUSE_SYMLINK ,
> +.BR FUSE_UNLINK ,
> +.B FUSE_WRITE
> .EE
> .in
> .SH SEE ALSO
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
