bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

"split --verbose" fails


From: Keith Thompson
Subject: "split --verbose" fails
Date: Thu, 26 Jun 2003 20:05:28 -0700
User-agent: Mutt/1.2.5i

The "--verbose" option to the "split" command doesn't work (where by
"doesn't work", I mean that specifying the option has no effect on the
command's output).

The problem seems to have been introduced in coreutils-4.5.10.  I see
the problem in releases 4.5.10 and 5.0; it works correctly in 4.5.9.

Behold:
========================================================================
% coreutils-4.5.9/bin/split --version | head -1
split (coreutils) 4.5.9
% coreutils-4.5.9/bin/split --verbose foo.txt
creating file `xaa'
creating file `xab'
% coreutils-4.5.10/bin/split --version | head -1
split (coreutils) 4.5.10
% coreutils-4.5.10/bin/split --verbose foo.txt
% coreutils-5.0/bin/split --version | head -1
split (coreutils) 5.0
% coreutils-5.0/bin/split --verbose foo.txt
========================================================================

I see the following in the ChangeLog:
========================================================================
2003-03-11  Jim Meyering  <address@hidden>
[...]
        * src/split.c (longopts): Don't hard-code `2' here.
        Instead, just specify `&verbose', and ...
        (main): ... remove the `case 2:' block for --verbose.
========================================================================

This is on Red Hat 9, but I see the same behavior in coreutils-5.0 on
Solaris 8.

I looked through the other coreutils sources for occurrences of the
same kind of longopts usage (using the address of the flag variable).
The only other case I found was su's --preserve-environment option,
but that seems to work correctly.

-- 
Keith Thompson (The_Other_Keith) address@hidden  <http://www.ghoti.net/~kst>
San Diego Supercomputer Center           <*>  <http://www.sdsc.edu/~kst>
Schroedinger does Shakespeare: "To be *and* not to be"




reply via email to

[Prev in Thread] Current Thread [Next in Thread]