rustc --print sysroot launches hyper (recursively, considering it's in my zshrc)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
- I am on the latest Hyper.app version
- 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
$PATHsuch thathyperopens 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 sysrootin hyper (when the line is not in my zshrc), one instance of the terminal pops up. At some pointrustc --print sysrootis starting the application in a manner similar to just typinghyper. - If I do any of this in alacritty, 0 issues occur. The
alacrittybinary is in the same place as thehyperAppImage ($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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Hyper AppImage launch behavior and the .zshrc line invoking rustc --print sysroot; reproduce the recursive windows in Hyper and compare the same command in Alacritty. Done means identifying whether Hyper is incorrectly launched by the command and documenting or fixing the interaction if it is within Hyper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, zsh
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100