manual: glob flags: fix sorting order

Reviewed-by: Carlos O'Donell <carlos@systemhalted.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
This commit is contained in:
Mike Frysinger 2012-12-21 00:03:17 -05:00
parent e557e9e519
commit aba5e59604
2 changed files with 12 additions and 7 deletions

View File

@ -1,3 +1,8 @@
2013-01-13 Mike Frysinger <vapier@gentoo.org>
* manual/pattern.texi (Flags for Globbing): Move GLOB_NOSORT after
GLOB_NOESCAPE.
2013-01-13 Mike Frysinger <vapier@gentoo.org>
* manual/pattern.texi (Flags for Globbing): Highlight GNU extensions.

View File

@ -493,13 +493,6 @@ as if it were a file name that had been matched. (Normally, when the
pattern doesn't match anything, @code{glob} returns that there were no
matches.)
@comment glob.h
@comment POSIX.2
@item GLOB_NOSORT
Don't sort the file names; return them in no particular order.
(In practice, the order will depend on the order of the entries in
the directory.) The only reason @emph{not} to sort is to save time.
@comment glob.h
@comment POSIX.2
@item GLOB_NOESCAPE
@ -514,6 +507,13 @@ If you use @code{GLOB_NOESCAPE}, then @samp{\} is an ordinary character.
@code{glob} does its work by calling the function @code{fnmatch}
repeatedly. It handles the flag @code{GLOB_NOESCAPE} by turning on the
@code{FNM_NOESCAPE} flag in calls to @code{fnmatch}.
@comment glob.h
@comment POSIX.2
@item GLOB_NOSORT
Don't sort the file names; return them in no particular order.
(In practice, the order will depend on the order of the entries in
the directory.) The only reason @emph{not} to sort is to save time.
@end vtable
@node More Flags for Globbing