Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Equivalent of set -- *(DN) in sh
19.01.2015, 19:02, "ZyX" <kp-pav@xxxxxxxxx>:
> 19.01.2015, 18:55, "ZyX" <kp-pav@xxxxxxxxx>:
>> 19.01.2015, 18:51, "ZyX" <kp-pav@xxxxxxxxx>:
>>> 18.01.2015, 23:53, "Eric Cook" <llua@xxxxxxx>:
>>>> On 01/18/2015 01:28 PM, Nikolai Weibull wrote:
>>>>> Hi!
>>>>>
>>>>> Is there any way to get the equivalent of Zsh’s
>>>>>
>>>>> set -- *(DN)
>>>>>
>>>>> in sh? Most important here would be NULL_GLOB, as, by default, sh
>>>>> simply leaves the * if there are no files to match.
>>>>>
>>>>> Thanks!
>>>> match() {
>>>> test "$#" -gt 2 && return
>>>> test -e "$1" && return
>>>> return 1
>>>> }
>>>>
>>>> set --
>>>> for pat in '.[^.]*' '*'; do # *(DN) ignores . and ..
>>> `..foo` is a valid name, but it is being excluded. You need to add `'.??*'` to the list of patterns.
>> No, this may make duplicates. Then `'..?*'`.
>
> And you must replace `[^.]` with `[!.]`. mksh does not support `[^]` and treats this as `[\^.]`, but other shells I have (dash, ksh, zsh (in sh emulation mode), bash, busybox ash) are fine with both `[!.]` and `[^.]`.
>>>> if match $pat; then
>>>> set -- "$@" $pat
>>>> fi
>>>> done
>>>> unset pat
>>>>
>>>> test "$#" -gt 0 && printf '%s\n' "$@"
Also note that if you need *full* equivalent of *(DN) you need to do something with ordering. I have checked all the shells with
for sh in dash ksh mksh zsh bash bb ; do $sh set--sDN.sh > set--sDN.$sh.log ; done
with
emulate -L sh &>/dev/null
match() {
test "$#" -gt 2 && return
test -e "$1" && return
return 1
}
set --
for pat in '.[!.]*' '..?*' '*'; do # *(DN) ignores . and ..
if match $pat; then
set -- "$@" $pat
fi
done
unset pat
test "$#" -gt 0 && printf '>>%s<<\n' "$@"
in set--sDN.sh file and have the following md5sums:
% md5sum set--sDN.*.log | sort
4601e6d9c845fe88e5166db3be04cc75 set--sDN.bash.log
4601e6d9c845fe88e5166db3be04cc75 set--sDN.ksh.log
4601e6d9c845fe88e5166db3be04cc75 set--sDN.zsh.log
ac2c245cdac664121a348c6b05ea2f44 set--sDN.bb.log
ac2c245cdac664121a348c6b05ea2f44 set--sDN.dash.log
ac2c245cdac664121a348c6b05ea2f44 set--sDN.mksh.log
: two variants of ordering:
bash/ksh/zsh:
>>.abc<<
>>.b<<
>>.^foo<<
>>..foo<<
>>
<<
>>1<<
>>17<<
>>2<<
>>append-remove.bash<<
>>getnumbers.bash<<
>>grepdir<<
>>nroff<<
>>parinput.bash<<
>>qwerty<<
>>rl.sh<<
>>script_path.bash<<
>>set--sDN.bash.log<<
>>set--sDN.bb.log<<
>>set--sDN.dash.log<<
>>set--sDN.ksh.log<<
>>set--sDN.mksh.log<<
>>set--sDN.sh<<
>>set--sDN.zsh.log<<
>>tes.bash<<
>>test<<
>>test2.bash<<
>>test3.bash<<
>>test.bash<<
>>testdir<<
>>test-rename.sh<<
>>test-so-2914220.bash<<
>>t.tar<<
>>ttttt.tar.bz2<<
>>ttttt.tar.gz<<
bb/dash/mksh:
>>.^foo<<
>>.abc<<
>>.b<<
>>..foo<<
>>
<<
>>1<<
>>17<<
>>2<<
>>append-remove.bash<<
>>getnumbers.bash<<
>>grepdir<<
>>nroff<<
>>parinput.bash<<
>>qwerty<<
>>rl.sh<<
>>script_path.bash<<
>>set--sDN.bash.log<<
>>set--sDN.bb.log<<
>>set--sDN.dash.log<<
>>set--sDN.ksh.log<<
>>set--sDN.mksh.log<<
>>set--sDN.sh<<
>>set--sDN.zsh.log<<
>>t.tar<<
>>tes.bash<<
>>test<<
>>test-rename.sh<<
>>test-so-2914220.bash<<
>>test.bash<<
>>test2.bash<<
>>test3.bash<<
>>testdir<<
>>ttttt.tar.bz2<<
>>ttttt.tar.gz<<
(note position of t.tar).
I have verified that all tests emit essentially the same result by using `for f in set--sDN.*.log ; do cat $f | sort | md5sum ; done | uniq`. But both orderings are different from the zsh one:
% zsh -f -c 'for f in *(DN); do echo ">>$f<<" ; done'
>>
<<
>>1<<
>>17<<
>>2<<
>>.abc<<
>>append-remove.bash<<
>>.b<<
>>.^foo<<
>>..foo<<
>>getnumbers.bash<<
>>grepdir<<
>>nroff<<
>>parinput.bash<<
>>qwerty<<
>>rl.sh<<
>>script_path.bash<<
>>set--sDN.bash.log<<
>>set--sDN.bb.log<<
>>set--sDN.dash.log<<
>>set--sDN.ksh.log<<
>>set--sDN.mksh.log<<
>>set--sDN.sh<<
>>set--sDN.zsh.log<<
>>tes.bash<<
>>test<<
>>test2.bash<<
>>test3.bash<<
>>test.bash<<
>>testdir<<
>>test-rename.sh<<
>>test-so-2914220.bash<<
>>t.tar<<
>>ttttt.tar.bz2<<
>>ttttt.tar.gz<<
(note: I have filename with newline, this is why I added `>><<`.)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author