From aba5e59604da465adc6eb65b33a414dfc29904de Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Fri, 21 Dec 2012 00:03:17 -0500 Subject: manual: glob flags: fix sorting order Reviewed-by: Carlos O'Donell Signed-off-by: Mike Frysinger --- ChangeLog | 5 +++++ manual/pattern.texi | 14 +++++++------- 2 files changed, 12 insertions(+), 7 deletions(-) diff --git a/ChangeLog b/ChangeLog index 55c36f2f7f..68b5d321f6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2013-01-13 Mike Frysinger + + * manual/pattern.texi (Flags for Globbing): Move GLOB_NOSORT after + GLOB_NOESCAPE. + 2013-01-13 Mike Frysinger * manual/pattern.texi (Flags for Globbing): Highlight GNU extensions. diff --git a/manual/pattern.texi b/manual/pattern.texi index 60e9dc864b..1966f3f148 100644 --- a/manual/pattern.texi +++ b/manual/pattern.texi @@ -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 -- cgit 1.4.1