rustc --print sysroot launches hyper (recursively, considering it's in my zshrc)

[rivertam]

• [x] I am on the latest Hyper.app version
• [x] I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Ubuntu 16.04
• Hyper.app version: 3.02
• Link of a Gist with the contents of your .hyper.js: I think this is just the default
• The issue is reproducible in vanilla Hyper.app: I think this is as vanilla as it gets.

Issue

This is perhaps one of the oddest bugs I've encountered, and I'm not sure it can be classified as a hyper issue, but I was hoping someone might be able to help me out here.

Fast facts:

• I'm "switching" (at least for a few minutes) from Alacritty
• To install hyper, I put the AppImage executable in my $PATH such that hyper 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, and taking it out "resolves" the initial issue, which is:
• 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 point rustc --print sysroot is starting the application in a manner similar to just typing hyper.
• If I do any of this in alacritty, 0 issues occur. The alacritty binary is in the same place as the hyper AppImage ($HOME/.bin/{alacritty,hyper}). If this were happening with alacritty, I wouldn't bother posting it in the hyper issues.

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. I've also posted this on the Rust forums

[rivertam]

This actually occurs whenever I use rustup as well. I suspect these tools call the terminal emulator binary with arguments that hyper ignores or something similar.

[rivertam]

This seems to not happen if I install using the deb instead of the AppImage.