From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 4/3] install/README: improve wording
Date: Tue, 17 Oct 2023 10:07:50 +0200 [thread overview]
Message-ID: <20231017100750+0200.545683-stepnem@smrk.net> (raw)
In-Reply-To: <20231017075428.M329380@dcvr>
On Tue, 17 Oct 2023 07:54:28 +0000
Eric Wong wrote:
>> > -* users using from git or tarballs (and not the OS package manager)
>> > +* users running our code from git or tarballs (and not the OS package manager)
>>
>> LGTM, but I'd also wrap the line (the text file line length
>> norm in the repo seems to lie between 60 and 70; this would
>> be 78).
>
> I think it's fine for a standalone lines such as list items to
> be up to 80. While paragraphs get harder to read with more
> columns, standalone lines get distracting when wrapped (IMHO).
I'd still at least make a distinction between "true" lists
such as the package listings in INSTALL (which are also
columnized, so the actual "line" is quite short), and what's
closer to just a sentence with a bullet point, like here.
In the given context I don't find
* users running our code from git or tarballs (and not the
OS package manager)
distracting, unlike the overlong line, but it's your call of
course.
--
Štěpán
prev parent reply other threads:[~2023-10-17 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:33 [PATCH 1/3] doc: fix some typos and grammar Štěpán Němec
2023-10-16 11:33 ` [PATCH 2/3] doc: lei-q: drop stale TODO comment (fixed in 1f1b1f0e22f7) Štěpán Němec
2023-10-16 21:17 ` Eric Wong
2023-10-16 11:33 ` [PATCH 3/3] search: rectify comment (rt: documented since 738c4a65719e) Štěpán Němec
2023-10-16 21:39 ` Eric Wong
2023-10-16 21:13 ` [PATCH 1/3] doc: fix some typos and grammar Eric Wong
2023-10-16 22:16 ` Štěpán Němec
2023-10-17 6:43 ` [PATCH 4/3] install/README: improve wording Eric Wong
2023-10-17 7:19 ` Štěpán Němec
2023-10-17 7:54 ` Eric Wong
2023-10-17 8:07 ` Štěpán Němec [this message]
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=20231017100750+0200.545683-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=e@80x24.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).