-
Notifications
You must be signed in to change notification settings - Fork 627
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
gem env home changed by tmuxinator #841
Comments
I hit this same issue after setting up a new machine last week and was able to get around it by uninstalling the Homebrew tmuxinator package and installing tmuxinator with Rubygems instead:
Everything now works for me. I'm not sure why the Homebrew package is not working correctly, but I wonder if the instructions should be removed from the readme or a warning added until this is fixed? |
Please feel free to submit a PR. |
Per tmuxinator#841, there might be issues when installing via HomeBrew. This PR adds a note indicating these issues and recommends installing for now with RubyGems until the issues are resolved.
Thanks, @ethagnawl. I opened #843. I also wanted to provide some additional context:
Issue faced: After installing tmuxinator with HomeBrew, tmuxinator itself worked fine, but gems I installed with After uninstalling tmuxinator from HomeBrew and reinstalling with RubyGems, the installation directory is correctly reported to be inside of |
Per #841, there might be issues when installing via HomeBrew. This PR adds a note indicating these issues and recommends installing for now with RubyGems until the issues are resolved.
I faced same issue as @stevehanson - but with |
The problem with Homebrew is that it doesn't link gems into As a workaround, one can simply add PS: I also use |
It seems like there's some discussion around this issue in Homebrew/homebrew-core#59484. It'd be great to see some kind of fix implemented in tmuxinator. I'm not sure what needs to be done, but it is convenient to use Homebrew to install tmuxinator because I don't need to worry about the gem disappearing when changing Ruby versions. |
My current workaround is to unset the If someone wanted a different value, I suppose you could just set it in a similar way. Examples: ~/.zshrc # Workaround for Homebrew tmuxinator issue
# https://github.com/Homebrew/homebrew-core/issues/59484
# https://discourse.brew.sh/t/why-does-tmuxinator-sets-gem-home/7296
unset -v GEM_HOME ~/.config/fish/config.fish if status is-interactive
# Workaround for Homebrew tmuxinator issue
# https://github.com/Homebrew/homebrew-core/issues/59484
# https://discourse.brew.sh/t/why-does-tmuxinator-sets-gem-home/7296
set -e GEM_HOME
end |
Is this still an issue? I'm having trouble reproducing it. This is from within the tmuxinator session: $ cat `which tmuxinator`
#!/bin/bash
GEM_HOME="/opt/homebrew/Cellar/tmuxinator/3.2.1/libexec" exec "/opt/homebrew/Cellar/tmuxinator/3.2.1/libexec/bin/tmuxinator" "$@"
$ gem env home
/Users/akofink/.rbenv/versions/3.3.3/lib/ruby/gems/3.3.0 |
Describe the bug
Tmuxinator is changing my gem location.
If I start up a tmux session using tmux instead of tmuxinator I get:
This matches what I get from outside of a tmux session.
Within a tmux session started by tmuxinator my gem env home gets set to:
To Reproduce
from a plain old command line (outside of a tmuxinator session)
run
gem env home
start a session using tmuxinator
run
gem env home
Expected behavior
the path returned by
gem env home
within a tmuxinator started tmux session should match the path returned from outside of a tmuxinator started session.Environment
tmuxinator 3.0.1
tmux 3.2a
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-darwin18]
MacOS 10.14.6
The text was updated successfully, but these errors were encountered: