Closed DanTheMinotaur closed 2 years ago
Hey @DanTheMinotaur Thanks for raising this. I wasn't aware of this quirk !! Any ideas as to why there is a different behaviour in different shells? We will fix it soon 😄
Hey @DanTheMinotaur Thanks for raising this. I wasn't aware of this quirk !! Any ideas as to why there is a different behaviour in different shells? We will fix it soon smile
@christyjacob4 According to wikipedia it comes from shell scripts, which need to interpret the first two bytes in a shell file, when being run in the kernel. Here's an explanation on stackoverflow
I wouldn't be an expert, but if I had to guess fish strictly interprets this rule, while bash doesn't.
@DanTheMinotaur Please let me know if this is still an issue with the latest CLI 0.15.0
@DanTheMinotaur can this be closed now?
@stnguyen90 all good now 👍
When executing appwrite in a non-bash shell (I'm using fish). It will respond with unknown error.
This is due to their being a newline before the shebang. It can be fixed by removing the newline.
/usr/local/bin/appwrite
Probably an non-issue but thought I'd leave it here if anyone else runs into this.