-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser not opening on Linux #4
Comments
@japrogramer continuing our discussion from rust-lang/rustup#1125, if you don't mind, I'd like you to check if my updated branch works for you by running the following commands. First, confirm the bug triggers on the
If you get the message Then, check if the
|
The first set of commands work.
and the second in the other branch also works
but still this doesnt
|
@japrogramer to be clear, the first set of commands opens your browser? If so, can you check if this command opens the docs in your browser (make sure to run on the
If all these commands work fine, then maybe the problem really is in rustup. |
Yes they work, But the rustup doc command doesn't Here the index page i created works and the one pointing to std doesnt
both files have the same permissions, and the std/index.html does have content |
Works Doesn't work works
|
Same issue here, the following works
but not
which opens KTorrent for me. I followed some instructions from
from My config: |
I was never able to reproduce this issue locally, unfortunately. Anyways, I released v0.5 of this crate about two weeks ago, and it changes the strategy on Linux such that the system |
as asked in here, i'll respond to this. I use WSL, and xdg-open-wsl (which i can call with |
@Erudyx Ah, WSL should work fine with the release of v0.5. Still, if you want to confirm it's fixed now you can run what I posted above:
|
Its working fine, but i dont i dont know why |
That's because the currently released version of rustup is using v0.4.1 of this crate. There hasn't been a rustup release since I made the PR updating to v0.5. |
ooooh i get it, so this gonna be fixed when the pr is accepted, thanks for your time! |
I'm closing this issue. Feel free to make a new issue if this is still a problem with the current version of the library. |
Under certain conditions, nothing happens when trying to open a website using
opener::open
, while manually usingxdg-open
works fine. I suspect this is due to spawning the command with a null stdout. This is the current code where the command is configured:The reason null stdout was used was to prevent polluting the user's terminal with output from xdg-open.
The text was updated successfully, but these errors were encountered: