(C {(echo)} {(hi)})
(command.SimpleCommand
words: [
(word.CompoundWord
parts: [(word_part.LiteralPart token:(token id:Lit_Chars val:echo span_id:0))]
)
(word.CompoundWord
parts: [(word_part.LiteralPart token:(token id:Lit_Chars val:hi span_id:2))]
)
]
)
oil AST
(C {(echo)} {(hi)})
oil AST
(command.SimpleCommand
words: [
(word.CompoundWord
parts: [(word_part.LiteralPart token:(token id:Lit_Chars val:echo span_id:0))]
)
(word.CompoundWord
parts: [(word_part.LiteralPart token:(token id:Lit_Chars val:hi span_id:2))]
)
]
)
OK ast-formats
===== Hello
hi
inside func
in subshell
another
ComSub
===== EMPTY
===== NO TRAILING NEWLINE
hi
OK osh-file
hi
inside func
in subshell
another
ComSub
ComSub
===== EMPTY
===== NO TRAILING NEWLINE
hi
hi
line continuation
two
here doc
command sub
OK osh-stdin
osh 'shopt' usage error: Invalid option 'globstar'
[osh] lisa ~/git/oilshell/oil$ hi
[osh] lisa ~/git/oilshell/oil$ ^D
osh 'shopt' usage error: Invalid option 'globstar'
[osh] lisa ~/git/oilshell/oil$ osh 'shopt' usage error: Invalid option 'globstar'
Line 1 of ''
;
^
Invalid word while parsing command
[osh] lisa ~/git/oilshell/oil$ [osh] lisa ~/git/oilshell/oil$ ^D
osh 'shopt' usage error: Invalid option 'globstar'
Line 1 of ''
;echo OIL OIL
^
Invalid word while parsing command
[osh] lisa ~/git/oilshell/oil$ [osh] lisa ~/git/oilshell/oil$ ^D
osh 'shopt' usage error: Invalid option 'globstar'
Line 1 of "Backticks at line -1 of 'TODO'"
echo "
^
Unexpected EOF reading double-quoted string that began here
[osh] lisa ~/git/oilshell/oil$ [osh] lisa ~/git/oilshell/oil$ ^D
OK osh-interactive
osh 'shopt' usage error: Invalid option 'globstar'
[osh] lisa ~/git/oilshell/oil$ one
OK exit-builtin-interactive
TESTRC$ ^D
osh$ ^D
OK rc-file
Usage: oil.ovm MAIN_NAME [ARG]...
MAIN_NAME [ARG]...
oil.ovm behaves like busybox. If it's invoked through a symlink, e.g. 'osh',
then it behaves like that binary. Otherwise the binary name can be passed as
the first argument, e.g.:
oil.ovm osh -c 'echo hi'
Usage: osh [OPTION]... SCRIPT [ARG]...
osh [OPTION]... -c COMMAND [ARG]...
osh accepts POSIX sh flags, with the following differences:
-n only validate the syntax. Also prints the AST.
--show-ast print the AST in addition to executing.
--ast-format what format the AST should be in
Usage: oil [OPTION]... SCRIPT [ARG]...
oil [OPTION]... -c COMMAND [ARG]...
TODO: any changes?
Usage: osh [OPTION]... SCRIPT [ARG]...
osh [OPTION]... -c COMMAND [ARG]...
osh accepts POSIX sh flags, with the following differences:
-n only validate the syntax. Also prints the AST.
--show-ast print the AST in addition to executing.
--ast-format what format the AST should be in
Usage: oil [OPTION]... SCRIPT [ARG]...
oil [OPTION]... -c COMMAND [ARG]...
TODO: any changes?
OK help
Line 1 of ''
echo; echo; |
^
Invalid word while parsing command
_tmp/osh-usage-noexec.txt appears empty, as expected
OK noexec-fails-properly
Oil version 0.6.pre17
Release Date: -
Arch: x86_64
OS: Linux
Platform: #46~16.04.1-Ubuntu SMP Thu May 3 10:06:43 UTC 2018
Compiler: GCC 5.4.0 20160609
Interpreter: CPython
Interpreter version: 2.7.12
Bytecode: -
OK version
All test/osh-usage.sh tests passed.