users/15350: explain rounding rules for size glob qualifier

This commit is contained in:
Peter Stephenson 2010-09-02 08:46:27 +00:00
parent 7fe494f27a
commit aa24f1a703
2 changed files with 17 additions and 5 deletions

View file

@ -1,3 +1,8 @@
2010-09-02 Peter Stephenson <pws@csr.com>
* users/15350: Doc/expn.yo: explain the strange rounding rules for
size glob qualifier.
2010-09-01 Peter Stephenson <pws@csr.com>
* 28188: Doc/Zsh/mod_complist.yo, Doc/Zsh/zle.yo: better
@ -13586,5 +13591,5 @@
*****************************************************
* This is used by the shell to define $ZSH_PATCHLEVEL
* $Revision: 1.5067 $
* $Revision: 1.5068 $
*****************************************************

View file

@ -2302,10 +2302,17 @@ time.
)
item(tt(L)[tt(PLUS())|tt(-)]var(n))(
files less than var(n) bytes (tt(-)), more than var(n) bytes (tt(PLUS())), or
exactly var(n) bytes in length. If this flag is directly followed by a `tt(k)'
(`tt(K)'), `tt(m)' (`tt(M)'), or `tt(p)' (`tt(P)') (e.g. `tt(Lk-50)')
the check is performed with kilobytes, megabytes, or blocks (of 512 bytes)
instead.
exactly var(n) bytes in length.
If this flag is directly followed by a `tt(k)' (`tt(K)'), `tt(m)'
(`tt(M)'), or `tt(p)' (`tt(P)') (e.g. `tt(Lk-50)') the check is performed
with kilobytes, megabytes, or blocks (of 512 bytes) instead. In this
case a file is regarded as "exactly" the size if the file size rounded up
to the next unit is equal to the test size. Hence `tt(*LPAR()Lm1+RPAR())'
matches files from 1 byte up to 1 Megabyte inclusive. Note also that
the set of files "less than" the test size only includes files that would
not match the equality test; hence `tt(*LPAR()Lm-1+RPAR())' only matches
files of zero size.
)
item(tt(^))(
negates all qualifiers following it