[Top][All Lists]

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

[Emacs-bug-tracker] bug#7241: closed (Possible bug on split ?)

From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#7241: closed (Possible bug on split ?)
Date: Tue, 31 May 2011 21:37:01 +0000

Your message dated Tue, 31 May 2011 23:36:15 +0200
with message-id <address@hidden>
and subject line Re: bug#7241: Possible bug on split ?
has caused the GNU bug report #7241,
regarding Possible bug on split ?
to be marked as done.

(If you believe you have received this mail in error, please contact

7241: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7241
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Possible bug on split ? Date: Mon, 18 Oct 2010 19:19:54 +0200 User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20100915 Thunderbird/3.1.4
 With split --help I get the information on units like K, KB, M, MB etc.

As split 123m and split 123MB work fine, but split 123mb doesn't, it seems, that the unit identifiers only partly work for lower-case letters.

IMO this is a bug, or should be documented more explicit.

What you think?


--- End Message ---
--- Begin Message --- Subject: Re: bug#7241: Possible bug on split ? Date: Tue, 31 May 2011 23:36:15 +0200
Ulf Zibis wrote:

>  Am 19.10.2010 21:24, schrieb Paul Eggert:
>> On 10/19/10 07:42, Ulf Zibis wrote:
>>> In many FAQs the small letter spelling is suggested, e.g.:
>>> ntfsclone -s -o -<source>  | gzip -c | split -a 3 -b 700m -<destination>
>>> So IMO small letter writing for "MB" should be allowed
>> But "mb" is SI syntax for "millibit", which
>> is a very small unit of information.  Having "mb"
>> be an alias for "megabyte" would be confusing
>> to those used to the standard notation.  (Having
>> "mb" be an alias for "megabit", or for "millibyte",
>> would be bad as well.)
>> We have to support plain "m" as an alias for "MiB",
>> because POSIX requires support for plain "m".
>> But let's not compound POSIX's mistake by supporting
>> even more usages that are contrary to SI.
> Ok, so the docs should be better detailed.
> BTW: this problem is not restricted on the split command, it concerns
> allmost all GNU coreutils and more, e.g. ntfsprogs.

The info documentation is very specific:

`-b SIZE'
     Put SIZE bytes of INPUT into each output file.  SIZE may be, or
     may be an integer optionally followed by, one of the following
     multiplicative suffixes:
          `b'  =>            512 ("blocks")
          `KB' =>           1000 (KiloBytes)
          `K'  =>           1024 (KibiBytes)
          `MB' =>      1000*1000 (MegaBytes)
          `M'  =>      1024*1024 (MebiBytes)
          `GB' => 1000*1000*1000 (GigaBytes)
          `G'  => 1024*1024*1024 (GibiBytes)
     and so on for `T', `P', `E', `Z', and `Y'.

However, split --help is brief (and split.1 is mechanically
derived from split --help output), but that's fine, because it's
more of a quick-reference and points to the info documentation.
Note the last line:

    For complete documentation, run: info coreutils 'split invocation'

We'd welcome any specific suggestions for improvement you may have.
Note that while I'm closing this "issue", you're welcome to continue
replying, and comments will still be archived for it and read by people
on this list.

--- End Message ---

reply via email to

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