This is perhaps one of the oddest bugs I've encountered, and I'm not sure it can be classified as a rustc issue, but I was hoping someone might be able to help me out here.
Fast facts:
- I'm trying out hyper terminal
- To install hyper, I put the AppImage executable in my
$PATH
such thathyper
opens the terminal - I use zsh, and my .zshrc includes the line
export RUST_SRC_PATH="$(rustc --print sysroot)/lib/rustlib/src/rust/src"
. This is the problematic line. - When I open a new instance of hyper, I get a recursive set of windows. I think 5 windows spawn, and the last one finally errors with
'hyper' is not installed for the toolchain 'nightly-x86_64-unknown-linux-gnu'
. Why the fifth window errors while the previous ones do not is beyond my understanding. - When I take the line out of my zshrc, the problem does not occur.
- If I just type
rustc --print sysroot
in hyper (when the line is not in my zshrc), one instance of the terminal pops up. At some pointrustc --print sysroot
is starting the application in a manner similar to just typinghyper
. - If I do any of this in alacritty, 0 issues occur. The
alacritty
binary is in the same place as thehyper
binary ($HOME/.bin/{alacritty,hyper}
)
Does anyone have any idea why this would happen or how I can fix it? It's worth noting that renaming the hyper AppImage to hyper2
does not resolve the problem.
EDIT: This occurs whenever I use rustup, actually. rustup --version
results in the same output as hyper --version
for some reason. I'm fairly confident the rustup
binary has not changed (last modified 18 Dec 2019, and using it in Alacritty yields normal behavior)
EDIT 2: This doesn't happen if I install using the deb instead of the AppImage...