Lines Matching refs:first
223 The first parts (@samp{foo}) are identical.
234 The first byte of the first string (@samp{.}) is compared
235 to the first byte of the second string (@samp{a}).
290 @samp{8.49} is numerically less than @samp{8.5}, and appears before first.
292 Version sort (@samp{sort -V}) first breaks down the string into digit and
296 Comparing the string @samp{8.1} to @samp{8.01}, first the
341 Hence, @file{1.0.5_src.tar.gz} is listed first.
345 than dot's ASCII value of 46), that file will be listed first:
390 a non-letter like @samp{%} -- hence @samp{az} appears first (despite
419 with a non-digit (@samp{~}). This is the first part. All other lines
420 in the input file start with a digit -- their first non-digit part is
425 and is listed first in the sorted output.
447 byte-by-byte, e.g., first @samp{0xCE} (decimal value 206) then
459 Ignoring the first letter (@samp{a}) which is identical in all
466 first byte of the UTF-8 sequence of @samp{α}, which is 0xCE or 206). The
564 first, followed by any hidden files (files starting with a dot),
657 first).
667 (@samp{hello-8.2} comes first).
688 @samp{.txt}) will determine that the shorter string comes first --
689 resulting in @file{hello-8.2.txt} appearing first.
707 being first.
712 @file{gcc_10.8.12.7rc2.fc9.tar.bz2} first, while @samp{ls -v} will list
713 @file{gcc_10.fc9.tar.gz} first.
798 output of @samp{ls -v} or @samp{sort -V}), please first check the following: