[Bug 16180] New: unexpand behaves oddly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=16180

            Bug ID: 16180
           Summary: unexpand behaves oddly
           Product: Busybox
           Version: 1.36.x
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Standard Compliance
          Assignee: unassigned at busybox.net
          Reporter: busybox131d at havu.ch
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

I was trying to use unexpand for a simple formatting of a file that was
indented with two spaces. I was using it just like this:

printf 'int main(void)\n' | unexpand -ft2

Everything seems alright there. I used to use the same arguments with GNU
coreutils, with the exception of -f being --first-only there. But oddly enough,
this prints the output:

int     main(void)

I mind you that the character between int and main is a tab. It does this for
every definition of that form. It does that for "class Foobar {}", too. I
tested if it was related to -f or -t, and surely enough, -t was at fault. -t
with values 1, 2, and 4 causes this strange bug. I tested up to 20.

My version of Busybox is 1.36.1 that comes with Alpine 3.20.

-- 
You are receiving this mail because:
You are on the CC list for the bug.