BARE_GLOB_QUAL

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Oct 5,  5:23pm, Zefram wrote:
}
} Bart Schaefer wrote:
} >Should we make BARE_GLOB_QUAL a bit smarter so that it knows about
} >KSH_GLOB and looks back one more character to see if what precedes the
} >open-paren token is one of the ksh-glob-chars?
} 
} With your proposed change, you'd have to think about the opposite
} ambiguity too -- a set of glob qualifiers might be interpreted as part of
} a pattern, and you'd sometimes need extra effort to force interpretation
} as glob qualifiers.  I recommend sticking with the current, simpler, rule.

That sounds fine to me.  In that case the doc for one or both of KSH_GLOB
and BARE_GLOB_QUAL should mention this.

} This is why we made the BARE_GLOB_QUAL option -- we wanted an unambiguous
} syntax for glob qualifiers, that wouldn't get in the way of globbing
} syntax at all.  Unfortunately no one's yet come up with a really good
} suggestion.

Hm.  We're using (#x) for various values of x to introduce things like
approximate completion, case-insensitive matching, and backrefs.  How
about (#q...) for qualifiers?  Also (#Q-) could turn off BARE_GLOB_QUAL,
and (#Q+) could turn it on.  (I can't decide which of those just (#Q)
should do.)

That would introduce the possibility of having different qualifiers for
different parts of the glob pattern, e.g. `*(#qG)/*(#q.^G)' would list
all plain files not owned by the current effective group that are in
directories that are owned by the current effective group.

Although implementation of that latter suggestion might be rather hairy.
For now, all (#q...) should simply be gathered up and applied at the end
as if they appeared in a single list.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net