From: Alejandro Colomar <alx.manpages@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Quentin Monnet <quentin@isovalent.com>, bpf <bpf@vger.kernel.org>,
linux-man <linux-man@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: [PATCH] Fit line in 80 columns
Date: Thu, 25 Aug 2022 23:51:26 +0200 [thread overview]
Message-ID: <403a8238-12e7-1092-a28b-a52f5d63df2c@gmail.com> (raw)
In-Reply-To: <CAEf4BzbCgHp0MtsSm_ExPO+EGhFWzLUOiFuh1jyrhWfbsDtL3A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1452 bytes --]
Hi Andrii and Alexei,
On 8/25/22 23:36, Andrii Nakryiko wrote:
> On Thu, Aug 25, 2022 at 11:07 AM Alexei Starovoitov
> <alexei.starovoitov@gmail.com> wrote:
>>
>> On Thu, Aug 25, 2022 at 11:02 AM Alejandro Colomar
>> <alx.manpages@gmail.com> wrote:
>>>
>>> That line is used to generate the bpf-helpers(7) manual page. It
>>> is a no-fill line, since it represents a command, which means that
>>> the formatter can't break the line, and instead just runs across
>>> the right margin (in most set-ups this means that the pager will
>>> break the line).
>>>
>>> Using <fmt> makes it end exactly at the 80-col right margin, both
>>> in the header file, and also in the manual page, and also seems to
>>> be a sensible name.
>>
>> Nack.
>>
>> We don't follow 80 char limit and are not going to because of man pages.
>
> And it's questionable in general to enforce line length for verbatim
> (code) block. It's verbatim for a good reason, it can't be wrapped.
That's why instead of wrapping, I reduced the length of some
"identifier". It's not enforced, but it's nicer if it fits. There are
several other cases, where it wasn't easy to make it shorter, and I left
it exceeding the margin.
It's not so crucial to fix it, and if you prefer it like it is
currently, it's reasonable. This is a suggestion, to make it easier to
read.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-25 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 17:56 [PATCH] Fit line in 80 columns Alejandro Colomar
2022-08-25 18:06 ` Alexei Starovoitov
2022-08-25 21:36 ` Andrii Nakryiko
2022-08-25 21:51 ` Alejandro Colomar [this message]
2022-08-25 21:54 ` Alejandro Colomar
2022-08-25 22:54 ` G. Branden Robinson
2022-08-26 0:25 ` Alexei Starovoitov
2022-08-26 0:45 ` Seth David Schoen
2022-08-27 7:20 ` Greg KH
2022-08-29 19:58 ` [PATCH v2] Fit lines " Alejandro Colomar
2022-08-29 20:29 ` Daniel Borkmann
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=403a8238-12e7-1092-a28b-a52f5d63df2c@gmail.com \
--to=alx.manpages@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.