jfly
commented
2 years ago That's interesting. I'm not able to reproduce the issue locally. I checked, and I also have a ~/.asdf/plugins/ruby/bin/exec-env file, and I'm guessing it looks identical to yours:
$ cat ~/.asdf/plugins/ruby/bin/exec-env
#!/usr/bin/env bash
current_script_path=${BASH_SOURCE[0]}
ruby_plugin_dir=$(dirname "$(dirname "$current_script_path")")
if [ "$RUBYLIB" = "" ]; then
export RUBYLIB="$ruby_plugin_dir/rubygems-plugin"
else
export RUBYLIB="$ruby_plugin_dir/rubygems-plugin:$RUBYLIB"
fi
export PATH=$install_path/bin:$PATHLine 6 is this if [ "$RUBYLIB" = "" ]; then, which does look like an unbound variable reference. If I add a set -u to the top of this script, I see the exact same behavior as you.
Wild guess: I wonder if there's something different between your bash and my bash, or their configurations that's causing yours to have bash's nounset behavior always turned on? What do you see if you create and run this dead simple bash script?
$ cat test.sh
#!/usr/bin/env bash
BOUND=42
echo "bound: $BOUND"
echo "unbound: $UNBOUND"
$ chmod +x ./test.sh
$ ./test.sh
bound: 42
unbound:And for the record, here's what my bash looks like:
$ bash --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
mchristen
BradenM
I have a .tool-versions file with
ruby 2.7.2in it and after runningasdf installdirenv reloadfails to load ruby with the following error. This also seems to happen to other plugins that export environment variables.If I inspect my cached env file from asdf-direnv 0.1.0 I can see that the last line has
export RUBYLIB=$'/home/developer/.asdf/plugins/ruby/rubygems-plugin:/home/developer/.asdf/plugins/ruby/rubygems-plugin'whereas the env file made by asdf-direnv 0.2.0 does not contain that line.