submitted 1 year ago* (last edited 1 year ago) by gamma@programming.dev to c/shell@programming.dev

5 comments fedilink hide all child comments

YSH, or the shell formally known as oil, is touted as a possible upgrade path from Bash.

This is the first in a three-part series of posts re-introducing the language.

you are viewing a single comment's thread
view the rest of the comments

[-] howarddo@programming.dev 1 points 1 year ago* (last edited 1 year ago)

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

[-] gamma@programming.dev 2 points 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;}

this post was submitted on 13 Jun 2023

3 points (100.0% liked)

Shell Scripting

1348 readers

4 users here now

Follow Lemmy rules!
Posts must relate to shell scripting. (See bottom of sidebar for more information.)
Only make helpful replies to questions. This is not the place for low effort joke answers.
No discussion about piracy or hacking.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!
These rules will change as the community grows.

Keep posts about shell scripting! Here are some guidelines to help:

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)

In general, if your submission text is primarily shell code, then it is welcome here!

founded 1 year ago

MODERATORS