[ysh] (1/3) Reviewing YSH

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I’m sure there’s a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

Gamma · edit-2 1 year ago

Howard Do · edit-2 1 year ago

At what is this better than zsh, bash or fish? What make u switch to ysh?

Gamma · 1 year ago

I haven’t switched to ysh. I personally use Zsh for my interactive shell, but I write my scripts in a variety of shells.

You can start with Ysh in its Bash-compatible mode, individually enable new features with shopt. Those features include:

Not splitting or globbing $foo by default (this is shared by Zsh and Fish)
A Python-inpsired parsing mode, which should supersede arithmetic mode (induced by ( ) in tests, $[ ] for string splicing and @[ ] for array splicing)
Strucutred data
New functions which return structured data (Oil calls classic shell functions “procs”, because they behave a lot like external programs with extra side effects)
cd to/somewhere { echo $PWD;}