MacOS - zsh - local & global installations not working #703
-
My I see there is some stuff in the readme about using shims, but I thought it's better not to use these ( Full |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
|
This works! So, I think there was some issue or user error with the homebrew setup. |
Beta Was this translation helpful? Give feedback.
-
|
when you install rtx via brew, rtx binary will install to |
Beta Was this translation helpful? Give feedback.
-
|
does |
Beta Was this translation helpful? Give feedback.
-
|
You're right: I can't explain what the heck I was trying/saying there 😁 somehow I tried a bunch of stuff but nothing worked. Definitely PEBCAK! FWIW, I did the brew install again; Brew doesn't suggest adding anything to ~/.zshrc (the I think that's what helped me get going smoothly with that install. So now ~.zshrc has |
Beta Was this translation helpful? Give feedback.
-
|
BTW, it looks like there's a few ways of doing things in the readme:
Amazing tool though! I was really happy with the templating - I just wrote a blog on it 😁 https://idiosapps.github.io/garden/rtx-asdf/ The key interesting bit is getting versions from various bits of source code, to prevent drift: [tools]
java = { version = "{{exec(command='head -1 docker/Dockerfile | cut -c 12- | tr : -')}}" }
mill = { version = "{{exec(command='echo $(cat .mill-version)')}}" }
scala = { version = "{{exec(command='grep -m 1 2.13 dependencies/Dependencies.sc | cut -c 33-39')}}" } |
Beta Was this translation helpful? Give feedback.
-
|
I saw another two things, apologies for so many replies:
If you think they're worthwhile issues, I can raise them later. The discussion got on a bit of a tangent as I tried to figure out why I got lost this morning with the brew rtx setup. |
Beta Was this translation helpful? Give feedback.
-
if for different shell , |
Beta Was this translation helpful? Give feedback.
-
|
@jdxcode I suggest |
Beta Was this translation helpful? Give feedback.
-
|
I also encountered this problem, and I wasted some time before finding this thread. I must admit that the thought of trying a different manager crossed my mind. I believe it would be worthwhile to link this thread in the quickstart guide. Maybe it's better to simply change the quickstart commands from: echo 'eval "$(~/bin/rtx activate bash)"' >> ~/.bashrc
echo 'eval "$(~/bin/rtx activate zsh)"' >> ~/.zshrc
echo '~/bin/rtx activate fish | source' >> ~/.config/fish/config.fishto: echo 'eval "$(rtx activate)"' >> ~/.bashrc
echo 'eval "$(rtx activate)"' >> ~/.zshrc
echo 'rtx activate | source' >> ~/.config/fish/config.fishWouldn't that possibly solve most of these types of issues? I personally on |
Beta Was this translation helpful? Give feedback.
-
|
In the quickstart you run the following commands: If |
Beta Was this translation helpful? Give feedback.
-
|
Oh yeah, I see this now. This was come from choosing a brew over curl. In any case, I think it would be worth pointing out somewhere that using homebrew, for example, will result in the need to adjust the rest of the instructions in quickstart. Personally, I always use brev whenever possible. And I don't recall ever having problems completing quickstarts using it. I understand that this is my mistake and perhaps a slight ignorance. However, simply mentioning it prominently could have helped avoid this problem. rtx looks like a great tool, I hope it develops quickly and a huge community is built around it. Somehow making sure future users never experience similar problems might help at least a little. All the best. |
Beta Was this translation helpful? Give feedback.
if
rtxis in your path, and you're using bash, justeval "$(rtx activate bash)is enough. ifrtxnot in your path, you have to use absolute path.for different shell ,
rtx activate SHELL_TYPEgenerates different output.