Why Create a New Unix Shell?

Re:Why Create a New Unix Shell? by CGamesPlay on Wednesday January 31, 2018 @03:57PM (#16277477)

> The only time I run into issues is when a command expects manipulate environment variables via bash syntax.

And in my experience 90% of those are in the form `FOO=bar command` which can be replaced with `env FOO=bar command` and works just fine in fish.

[ Parent | on HN ]

Re:Why Create a New Unix Shell? by ComputerGuru on Wednesday January 31, 2018 @06:04PM (#16278374)

Both support for `&&` and `||` (instead of `and` and `or`) as well as supporting `FOO=bar command` are under consideration for fish 3.0 to ease the migration path. The former is pretty much going to happen, the latter if we get around to it, DV.

[ Parent | on HN ]

Re:Why Create a New Unix Shell? by geewee on Thursday February 01, 2018 @02:16AM (#16280148)

This would be much appreciated. I know there are a few people on my team that cam't use fish due to our npm scripts needing to be compatible with cmd

[ Parent | on HN ]

Re:Why Create a New Unix Shell? by ComputerGuru on Friday February 02, 2018 @10:25AM (#16291207)

Why don’t your npm scripts specify /bin/sh as the interpreter?

[ Parent | on HN ]

Re:Why Create a New Unix Shell? by defined on Wednesday January 31, 2018 @10:05PM (#16279391)

Where things get problematic is with commands that send a set of environment variables to stdout, like

    eval $(ssh-agent)

Sure you can get addons (like bass[0]) that will translate the sh environment variable settings to fish, but it’s a pain to have to do that (and remember wth it was called).

[0] https://github.com/edc/bass

[ Parent | on HN ]