Pádraig Brady <[email protected]> writes: > On 26/11/2025 02:38, Collin Funk wrote: >> Collin Funk <[email protected]> writes: >> >>>> diff --git a/src/fold.c b/src/fold.c >>>> index 6dbf013e2..075dc7532 100644 >>>> --- a/src/fold.c >>>> +++ b/src/fold.c >>>> @@ -88,7 +88,7 @@ Wrap input lines in each FILE, writing to standard >>>> output.\n\ >>>> fputs (_("\ >>>> -b, --bytes count bytes rather than columns\n\ >>>> -c, --characters count characters rather than columns\n\ >>>> - -s, --spaces break at spaces\n\ >>>> + -s, --spaces break after blanks, or in words > WIDTH\n\ >>>> -w, --width=WIDTH use WIDTH columns instead of 80\n\ >>>> "), stdout); >>>> fputs (HELP_OPTION_DESCRIPTION, stdout); >>> >>> I think "words longer than WIDTH" is a bit more clear than "words >>> greater than WIDTH". WDYT? >> Actually, length is incorrect since we might be operating on columns >> occupied by the characters. So "wider" is probably more correct. > > Well the quantity can be bytes, characters, or columns, > so I was using "greater than" to cater to all those. > I _have_ changed from ">" to "greater than" as it fits > and is easier to read for some, and pushed.
That works for me, thanks. Collin
