*** Running test-ast-formats (command.Simple blame_tok: more_env: [] words: [{} {}] do_fork: T ) (command.Simple blame_tok: (Token id:Id.Lit_Chars length:4 col:0 line:(SourceLine line_num:1 content:"echo hi" src:(source__CFlag))) more_env: [] words: [ (CompoundWord parts:[...0x7f307fe4c4c8]) (CompoundWord parts:[(Token id:Id.Lit_Chars length:2 col:5 line:...0x7f307fe4ac00)]) ] do_fork: T ) oil AST 
(command.Simple
  blame_tok: <Id.Lit_Chars echo>
  more_env: []
  words: [{<Id.Lit_Chars echo>} {<Id.Lit_Chars hi>}]
  do_fork: T
)
oil AST 
(command.Simple
  blame_tok: (Token id:Id.Lit_Chars length:4 col:0 line:(SourceLine line_num:1 content:"echo hi" src:(source__CFlag)))
  more_env: []
  words: [
    (CompoundWord parts:[...0x7f91c0a984c8])
    (CompoundWord parts:[(Token id:Id.Lit_Chars length:2 col:5 line:...0x7f91c0a96c00)])
  ]
  do_fork: T
)
OK test-ast-formats *** Running test-exit-builtin-interactive osh-0.22.0$ one OK test-exit-builtin-interactive *** Running test-help Oils 0.22.0 https://www.oilshell.org/ ~~~ oils-usage ~~~ bin/oils-for-unix is an executable that contains OSH, YSH, and more. Usage: oils-for-unix MAIN_NAME ARG* MAIN_NAME ARG* It behaves like busybox. The command name can be passed as the first argument: oils-for-unix ysh -c 'echo hi' More commonly, it's invoked through a symlink like 'ysh', which causes it to behave like that command: ysh -c 'echo hi' Oils 0.22.0 https://www.oilshell.org/ ~~~ osh-usage ~~~ bin/osh is compatible with POSIX shell, bash, and other shells. Usage: osh FLAG* SCRIPT ARG* osh FLAG* -c COMMAND ARG* osh FLAG* The command line accepted by `bin/osh` is compatible with /bin/sh and bash. osh -c 'echo hi' osh myscript.sh echo 'echo hi' | osh It also has a few enhancements: osh -n -c 'hello' # pretty-print the AST osh --ast-format text -n -c 'hello' # print it full osh accepts POSIX sh flags, with these additions: -n parse the program but don't execute it. Print the AST. --ast-format what format the AST should be in Oils 0.22.0 https://www.oilshell.org/ ~~~ ysh-usage ~~~ bin/ysh is the shell with data tYpes, influenced by pYthon, JavaScript, ... Usage: ysh FLAG* SCRIPT ARG* ysh FLAG* -c COMMAND ARG* ysh FLAG* `bin/ysh` is the same as `bin/osh` with a the `ysh:all` option group set. So `bin/ysh` also accepts shell flags. ysh -c 'echo hi' ysh myscript.ysh echo 'echo hi' | ysh Oils 0.22.0 https://www.oilshell.org/ ~~~ osh-usage ~~~ bin/osh is compatible with POSIX shell, bash, and other shells. Usage: osh FLAG* SCRIPT ARG* osh FLAG* -c COMMAND ARG* osh FLAG* The command line accepted by `bin/osh` is compatible with /bin/sh and bash. osh -c 'echo hi' osh myscript.sh echo 'echo hi' | osh It also has a few enhancements: osh -n -c 'hello' # pretty-print the AST osh --ast-format text -n -c 'hello' # print it full osh accepts POSIX sh flags, with these additions: -n parse the program but don't execute it. Print the AST. --ast-format what format the AST should be in Oils 0.22.0 https://www.oilshell.org/ ~~~ oils-usage ~~~ bin/oils-for-unix is an executable that contains OSH, YSH, and more. Usage: oils-for-unix MAIN_NAME ARG* MAIN_NAME ARG* It behaves like busybox. The command name can be passed as the first argument: oils-for-unix ysh -c 'echo hi' More commonly, it's invoked through a symlink like 'ysh', which causes it to behave like that command: ysh -c 'echo hi' OK test-help *** Running test-noexec-fails-properly echo; echo; | ^ [ -c flag ]:1: Invalid word while parsing command _tmp/osh-usage-noexec.txt appears empty, as expected OK test-noexec-fails-properly *** Running test-osh-file ===== Hello hi inside func in subshell another ComSub ===== EMPTY ===== NO TRAILING NEWLINE hi OK test-osh-file *** Running test-osh-interactive osh-0.22.0$ hi osh-0.22.0$ ^D osh-0.22.0$ osh-0.22.0$ ; ^ [ stdin -i ]:1: Invalid word while parsing command osh-0.22.0$ ^D osh-0.22.0$ ;echo OIL OIL ^ [ stdin -i ]:1: Invalid word while parsing command osh-0.22.0$ ^D osh-0.22.0$ osh-0.22.0$ ^D OK test-osh-interactive *** Running test-osh-stdin hi inside func in subshell another ComSub ===== EMPTY ===== NO TRAILING NEWLINE hi hi line continuation two here doc command sub OK test-osh-stdin *** Running test-rc-file TESTRC$ ^D osh-0.22.0$ ^D osh-0.22.0$ ^D OK test-rc-file *** Running test-version Oils 0.22.0 https://www.oilshell.org/ Release Date: - Arch: x86_64 OS: Linux Platform: #25~22.04.1-Ubuntu SMP Mon Jun 17 18:38:57 UTC 2024 Compiler: GCC 8.3.0 Interpreter: CPython Interpreter version: 2.7.16 Bytecode: - OK test-version test/osh-usage.sh: 9 tests passed.