mise: `rtx activate bash` and PATH inconsistencies

I use bash as my login shell, and as such have placed eval "$(rtx activate bash)" in my .bashrc. The unexpected thing is that doing so adds each runtime’s binary path to the shell, as shown

/home/karan/.local/share/rtx/installs/nodejs/19.3.0/bin:/home/karan/.local/share/rtx/installs/poetry/1.3.1/bin:/home/karan/.local/share/rtx/installs/rust/stable/bin:/home/karan/.local/share/rtx/installs/leiningen/2.10.0/bin:/home/karan/.local/share/rtx/installs/php/8.2.3/bin:/home/karan/.local/share/rtx/installs/php/8.2.3/sbin:/home/karan/.local/share/rtx/installs/php/8.2.3/.composer/vendor/bin:/home/karan/.local/share/rtx/installs/tokei/12.1.2/bin:/home/karan/.local/share/rtx/installs/zoxide/0.9.0/bin:/home/karan/.local/share/rtx/installs/yarn/1.22.19/bin:/home/karan/.local/bin:/home/karan/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/lib/snapd/snap/bin:/home/karan/.yarn/bin:/home/karan/.yarn/bin

I don’t believe this is the intended behavior? I can say that that specific line produces this output becomes removing it and logging back in again does not produce this PATH.

Not sure what’s going on here, but any help is appreciated. Please do let me know if any other information is required.

Info: rtx ver: 1.16.1 shell: bash 5.2.15 OS: linux-x64 (Fedora 37)

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 22 (14 by maintainers)

Commits related to this issue

Most upvoted comments

updated the README to be less tmux specific

oh I see the problem, you’re trying to execute zoxide right away. I think I know what is missing here. I’ll work up a PR.

Apologies for not looking closer, I thought the issue was that it wasn’t on PATH after the rc file.