-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proper fix for dirname in env.sh #23
Comments
I was able to reproduce the error somehow:
So in some cases bash has |
So IMHO |
Maybe this could be a solution (please try an report, if it works):
|
Create
This will produce:
I hope this makes it clear. |
So in |
|
yepp, nonsense :-/ |
maybe we should go with ${BASH_SOURCE[0]-$0} then
|
* #21: improve OS support #23: proper fix for dirname of sourced script * #21: iTerm2 support with tabs now working * #21: improved windows documentation * #21: improve Mac support * #21: improved Mac Readme * #21: Improved IDEenv for linux/Mac * #21: fixed assembly packaging for OS variants, improved Mac keybindings
fixed with PR #21 |
User @maihacke changed
env.sh
to use$(dirname "$0")
:b9cca78#diff-59bbdf4f0007715da1871587ba4ffd3d
I assume this was some kind of bugfix for MacOS. Also this seems more reliable to me as
$BASH_SOURCE
is proprietary and only works in bash. What is the purpose why this was ever changed to this?User @vapadwal wants to change
env.sh
back to$(dirname "$BASH_SOURCE")
:985a51e#diff-59bbdf4f0007715da1871587ba4ffd3d
As I do not like to have git wars, I would kindly ask all participants to clarify the reasons for these changes and find a peaceful solution.
The text was updated successfully, but these errors were encountered: