diff options
Diffstat (limited to 'Test/E01options.ztst')
| -rw-r--r-- | Test/E01options.ztst | 51 |
1 files changed, 25 insertions, 26 deletions
diff --git a/Test/E01options.ztst b/Test/E01options.ztst index 1126dfdab..1d5fa2ad0 100644 --- a/Test/E01options.ztst +++ b/Test/E01options.ztst @@ -133,7 +133,7 @@ print [b 1:BAD_PATTERN option >[a -?ZTST_execchunk:2: bad pattern: [b +?ZTST_execchunk:4: bad pattern: [b unsetopt bareglobqual nomatch print *(.) @@ -192,8 +192,8 @@ 1q:CDABLE_VARS option >`print -P '%~'`/tmpcd >back in options.tmp -?ZTST_execchunk:cd:2: no such file or directory: cdablevar1 -?ZTST_execchunk:cd:2: no such file or directory: cdablevar2 +?ZTST_execchunk:cd:4: no such file or directory: cdablevar1 +?ZTST_execchunk:cd:10: no such file or directory: cdablevar2 # CHASE_DOTS should go with CHASE_LINKS in B01cd.ztst # which saves me having to write it here. @@ -227,8 +227,8 @@ >wimpole >royston >foxton -?ZTST_execchunk:2: file exists: foo1 -?ZTST_execchunk:2: no such file or directory: bar1 +?ZTST_execchunk:4: file exists: foo1 +?ZTST_execchunk:6: no such file or directory: bar1 setopt cshjunkieloops eval 'for f in swaffham bulbeck; print $f; end' @@ -239,7 +239,7 @@ >swaffham >bulbeck ?next one should fail -?ZTST_execchunk:-1: parse error near `end' +?ZTST_execchunk:1: parse error near `end' setopt cshjunkiequotes print this should cause an error >&2 @@ -253,7 +253,7 @@ >line three > line four ?this should cause an error -?ZTST_execchunk:-1: unmatched ' +?ZTST_execchunk:1: unmatched ' ?this should not nullcmd() { print '$NULLCMD run'; } @@ -279,10 +279,10 @@ >Running $READNULLCMD >$NULLCMD run ?This should fail -?ZTST_execchunk:2: redirection with no command +?ZTST_execchunk:8: redirection with no command ?This should succeed ?This should also fail -?ZTST_execchunk:2: redirection with no command +?ZTST_execchunk:13: redirection with no command # nomatch should be overridden by cshnullglob setopt nomatch cshnullglob @@ -297,7 +297,7 @@ >tmpcd tmpfile1 tmpfile2 blah >tmpcd tmpfile1 tmpfile2 nothing* blah >nothing* blah -?hoping for no match: ZTST_execchunk:2: no match +?hoping for no match: ZTST_execchunk:4: no match ? # The trick is to avoid =cat being expanded in the output while $catpath is. @@ -625,7 +625,7 @@ print with nomatch flooble* 1:NOMATCH option >with nonomatch: flooble* -?ZTST_execchunk:2: no matches found: flooble* +?ZTST_execchunk:4: no matches found: flooble* # NULL_GLOB should override NONOMATCH... setopt nullglob nomatch @@ -688,7 +688,7 @@ >File in upper dir >File in lower dir >unsetting option... -?ZTST_execchunk:2: no such file or directory: pathtestdir/findme +?ZTST_execchunk:14: no such file or directory: pathtestdir/findme setopt posixbuiltins command print foo @@ -698,7 +698,7 @@ 127:POSIX_BUILTINS option >foo >unsetting... -?ZTST_execchunk:2: command not found: print +?ZTST_execchunk:5: command not found: print # This option seems to be problematic. I don't quite know how it works. ## func() { @@ -807,7 +807,7 @@ >one'quoted'expression >anotherquotedexpression - # too lazy to test jobs -Z and ARGV0. +# too lazy to test jobs -Z and ARGV0. (setopt restricted; cd /) (setopt restricted; PATH=/bin:/usr/bin) (setopt restricted; /bin/ls) @@ -817,13 +817,13 @@ (setopt restricted; unsetopt restricted) : 0:RESTRICTED option -?ZTST_execchunk:cd:2: restricted +?ZTST_execchunk:cd:1: restricted ?ZTST_execchunk:2: PATH: restricted -?ZTST_execchunk:2: /bin/ls: restricted -?ZTST_execchunk:hash:2: restricted: /bin/ls -?ZTST_execchunk:2: writing redirection not allowed in restricted mode -?ZTST_execchunk:exec:2: ls: restricted -?ZTST_execchunk:unsetopt:2: can't change option: restricted +?ZTST_execchunk:3: /bin/ls: restricted +?ZTST_execchunk:hash:4: restricted: /bin/ls +?ZTST_execchunk:5: writing redirection not allowed in restricted mode +?ZTST_execchunk:exec:6: ls: restricted +?ZTST_execchunk:unsetopt:7: can't change option: restricted fn() { print =ls ={ls,} @@ -909,10 +909,9 @@ >nonsense >nonsense >nonsense -?fn:-1: parse error near `print' -?fn:-1: parse error near `print' -?fn:-1: parse error near `print' -# Eugh, that line numbering behaviour with eval is probably a bug. +?fn:1: parse error near `print' +?fn:1: parse error near `print' +?fn:1: parse error near `print' fn() { print -l $*; } setopt shwordsplit @@ -959,6 +958,6 @@ 0:XTRACE option >message >message -?+ZTST_execchunk:2> fn +?+ZTST_execchunk:3> fn ?+fn:0> print message -?+ZTST_execchunk:2> unsetopt xtrace +?+ZTST_execchunk:4> unsetopt xtrace |