Date: Tue, 23 Jun 2026 12:05:48 -0300 From: Benedict Reuschling <bcr@freebsd.org> To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@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: <19ea0bf3-a3f0-42d7-82b1-7ccc14659b0b@freebsd.org> In-Reply-To: <86h5mtpb2x.fsf@ltc.des.dev> References: <6a3a8793.3a6b0.3f275318@gitrepo.freebsd.org> <86ldc5pbxq.fsf@ltc.des.dev> <7c836803-b1fe-4978-94ea-5ab37d1427d8@freebsd.org> <86h5mtpb2x.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
Am 23.06.26 um 11:48 schrieb Dag-Erling Smørgrav: > 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. Alright, then let's do that to let the script be a bit more robust and user-friendly at the same time. > >> 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 Great, I like that. So we remove my addition again or how do we handle it? Benedicthome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19ea0bf3-a3f0-42d7-82b1-7ccc14659b0b>