[Bug 252896] usr.bin/cut when used with -w will replace first delimiter with \t delimter

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 20 Aug 2021 10:54:48 UTC

dsdqmhsx@aetern.org changed:

           What    |Removed                     |Added
                 CC|                            |dsdqmhsx@aetern.org

--- Comment #1 from dsdqmhsx@aetern.org ---
The question is what to assume as output field delimiter in -w case, as it
consumes whitespace/tab sequence as input one -- -w is not standard, and is not
supported in GNU version of cut (i.e. we have nothing to compare behavior

What you are showing seems to be the corner case (and, possibly, a real bug) of
using 'x-' range; if you use any other, e.g. 1,2,3,... or 1-10, all output
seems to be delimited by tab characters.

More so, example output you are providing is not correct, x+1..x+2..x+n fields
are not delimited by single whitespace, and rather keep the original number of
whitespaces between them.

You are receiving this mail because:
You are the assignee for the bug.