Live data from Hacker News

Elvish – Scripting language and interactive shell

github.com

61–62 of 62 posts

Re: Elvish – Scripting language and interactive shell

#61
post #60
post #52

Earlier quoted context omitted.

> You didn't answer my question about if `bg` returns a `fid` or not, and the documentation doesn't answer this either, nor did you say if those could be used in scripts... but it sounds like you're saying I have to parse `jobs` to get the `fid` of the command I just launched? Everything in the documentation can be used in scripts. `bg` doesn't write anything to stdout. The documentation does actually answer that if…

Awesome, thanks for the answers! It looks like Murex will be the first shell I try once I recharge my "rip everything up and start over" batteries again. > I know you weren't talking about arrays, but the next question people ask is "how do I now expand one variable to be multiple parameters?" I held back from asking that, but yes, exactly :P

Awesome. Good luck if/when you do. And feel free to pester me on Github with any questions / feedback / complaints you have :)

Re: Elvish – Scripting language and interactive shell

#62
After getting frustrated with how unusual and convoluted BASH syntax tends to be, especially with involved scripts, I've tried almost all of the alternative shells: Elvish, Fish, Oil, Xonsh (Python!), Emacs's eshell, and even the Haskell-based shell repls like Turtle and Shelly. The only one I really stuck with was Nushell. It's friendly, pretty, intuitive, easy to read, heavy on pipes, and super powerful for data analysis. Plus it's modern replacement for a lot of tools, like `ls`, `jq`, `curl`, and so on. Writing a little command-line program is a joy in Nushell.
Post reply on HN