I discovered that bass produces a bad script when running a bash script that exports (creates or updates) an environment variable whose value is multiple lines.
For example, this bash script:
export MULTILINE_VAR=$(echo -e "foo\nbar\nbaz")
produces this fish script:
# adding MULTILINE_VAR=foo
bar
baz
Running the script then results in bar: command not found and baz: command not found because those lines aren't commented out.
edc
commented
7 years ago
I discovered that bass produces a bad script when running a bash script that exports (creates or updates) an environment variable whose value is multiple lines.
For example, this bash script:
produces this fish script:
Running the script then results in
bar: command not foundandbaz: command not foundbecause those lines aren't commented out.This PR fixes that.