PATCH: Use new array syntax in _getconf

PATCH: Use new array syntax in _getconf

[Mikael Magnusson]

tried git grep --cached '(j\(.\)|\1)' and looked through the matches, this
was the only one that was obvious (to me) to convert to the new syntax.

---
 Completion/Unix/Command/_getconf |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Completion/Unix/Command/_getconf b/Completion/Unix/Command/_getconf
index 76d9c76..f2c713a 100644
--- a/Completion/Unix/Command/_getconf
+++ b/Completion/Unix/Command/_getconf
@@ -27,7 +27,7 @@ if [[ CURRENT -eq 2 ]]; then
   _tags syswideconfig pathconfig standardsconfig confstring restconfig
 
   allkeys=(${${(f)"$(getconf -a 2>/dev/null)"}%%[: ]*})
-  restkeys=(${allkeys:#(${(j.|.)~mykeys})})
+  restkeys=(${allkeys:|mykeys})
 
   while _tags; do
     _requested -V syswideconfig expl 'systemwide configuration variables' \
-- 
1.7.10.GIT

Re: PATCH: Use new array syntax in _getconf

[Bart Schaefer]

On Apr 27,  9:13am, Mikael Magnusson wrote:
}
} tried git grep --cached '(j\(.\)|\1)' and looked through the matches, this
} was the only one that was obvious (to me) to convert to the new syntax.

Yeah, the other places are going to be non-obvious -- pipes into grep,
or loops over the array.

I think in previoius email I was remembering the inner "for" loop in
__git_files_relative, but now I look again that's doing character slices,
not real arrays.  Similar application of pattern matching but not really
applicable to this new syntax.