You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
David Sweeney in this Elixir Forum post recently discovered the issue that our language_server.sh is no longer sh compatible because asdf (added in #78) is not currently sh compatible.
The error manifests itself with an error like: /home/my_home/.asdf/asdf.sh: 8: /home/my_home/.asdf/asdf.sh: Bad substitution
I have raised an issue on asdf to determine if asdf is meant to support sh/dash, or only bash and other shells.
I see a few possible ways forward but would like to collect other's thoughts about them:
Change language_server.sh to run bash instead of sh (via #!/usr/bin/env bash)
I'm currently leaning towards option 1 because bash is very widespread at this point and I'd imagine most systems will have it and for any that don't, the user will most likely understand how to fix the error.
The text was updated successfully, but these errors were encountered:
I think it's fine to require bash on a system running elixir-ls --- sh compatibility is desirable, but not a need for us. As you said, bash is pretty much today's sh.
While this lowers compatability somewhat, any system that a developer is
actively using is expected to have bash installed. This change is required
because asdf does not currently support sh, only bash and other more advanced
shells.
Fixes#114
David Sweeney in this Elixir Forum post recently discovered the issue that our
language_server.sh
is no longer sh compatible becauseasdf
(added in #78) is not currently sh compatible.The error manifests itself with an error like:
/home/my_home/.asdf/asdf.sh: 8: /home/my_home/.asdf/asdf.sh: Bad substitution
I have raised an issue on asdf to determine if asdf is meant to support sh/dash, or only bash and other shells.
I see a few possible ways forward but would like to collect other's thoughts about them:
language_server.sh
to run bash instead of sh (via#!/usr/bin/env bash
)I'm currently leaning towards option 1 because bash is very widespread at this point and I'd imagine most systems will have it and for any that don't, the user will most likely understand how to fix the error.
The text was updated successfully, but these errors were encountered: