Date: Tue, 23 Jun 2026 16:48:06 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Benedict Reuschling <bcr@freebsd.org> Cc: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 15a1ba4a1c46 - main - adduser.sh: Add info which separator to use in the question itself Message-ID: <86h5mtpb2x.fsf@ltc.des.dev> In-Reply-To: <7c836803-b1fe-4978-94ea-5ab37d1427d8@freebsd.org> (Benedict Reuschling's message of "Tue, 23 Jun 2026 11:45:40 -0300") References: <6a3a8793.3a6b0.3f275318@gitrepo.freebsd.org> <86ldc5pbxq.fsf@ltc.des.dev> <7c836803-b1fe-4978-94ea-5ab37d1427d8@freebsd.org>
index | next in thread | previous in thread | raw e-mail
Benedict Reuschling <bcr@freebsd.org> writes:
> Dag-Erling Smørgrav <des@freebsd.org> writes:
> > We could just as easily normalize the separator:
> That's true and would be the "src" way of solving it, rather than the
> "doc" way of describing what to do.
> I've seen instances where people even did "wheel, operator" (extra
> whitespace after the ",").
Yes, and my proposed change handles that transparently.
> I think when we actually tell people what to use as the separator,
> then we don't have to account for all kinds of varieties that users
> come up with to separate the groups (semicolons?).
Why not both? We can easily support colons and semicolons as well:
$ echo "foo, bar:baz; quux" | tr -s ':;,' ' '
foo bar baz quux
DES
--
Dag-Erling Smørgrav - des@FreeBSD.org
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86h5mtpb2x.fsf>