From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stepnem@smrk.net>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS20473 45.76.80.0/20
X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6
Received: from mail.smrk.net (mail.smrk.net [45.76.87.244])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 099451F406
	for <meta@public-inbox.org>; Tue, 17 Oct 2023 08:07:52 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=smrk.net header.i=@smrk.net header.a=rsa-sha256 header.s=20221002 header.b=INNzMFik;
	dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smrk.net; s=20221002;
	t=1697530071;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=DSIVEi3NLNrUjsvz/AUNl1nDo4eTpkAuEVIE1sEdHYU=;
	b=INNzMFiknOKxydgSYRAj89Vw2olPZlxoxBudNpx0Cmp7lWjLhb0We1/gTgfENidmnDByn6
	u1KyVyN3UZCQAxExrjEusXYHsZuVXmw1t3BQbfShnd1vGuIVLQp/SsU8L3CDzpShrHRtON
	evj/C6XqtnB3sK+mvSY7NATc/DsGwUiqedPjIj+8EBVh8f+4MQhjY5gvk0ScC/hv/k0M4c
	94GH0ToLrwDcK39d0zuUM0/7fH/3tgwodWNLKPuveGd1spH6yriBk/YIx54IDL3hlEu0x5
	RqMlwtnNnIN2oNbkrRPfnd5Oy9HhyLvmXif7L1xwhnVR7Kt250JUmbuZ70JTSQ==
Received: from localhost (<unknown> [192.168.5.2])
	by smrk (OpenSMTPD) with ESMTPSA id e1471b54 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO);
	Tue, 17 Oct 2023 10:07:51 +0200 (CEST)
From: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 4/3] install/README: improve wording
In-Reply-To: <20231017075428.M329380@dcvr>
References: <20231016113304.2788497-1-stepnem@smrk.net>
 <20231016211320.M268439@dcvr>
 <20231017001619+0200.395012-stepnem@smrk.net>
 <20231017064318.M245732@dcvr>
 <20231017091901+0200.985021-stepnem@smrk.net>
 <20231017075428.M329380@dcvr>
User-Agent: Notmuch/0.38 (https://notmuchmail.org) Emacs/30.0.50
 (x86_64-pc-linux-gnu)
Date: Tue, 17 Oct 2023 10:07:50 +0200
Message-ID: <20231017100750+0200.545683-stepnem@smrk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <meta.public-inbox.org>

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)
>>=20
>> 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.

--=20
=C5=A0t=C4=9Bp=C3=A1n