4 ms·

> 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

> 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.

ComputerGuru 9y ago
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.
- geewee 9y ago
  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
  - ComputerGuru 9y ago
    Why don’t your npm scripts specify /bin/sh as the interpreter?
defined 9y ago
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 https://github.com/edc/bass