We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the issue I'm not sure if it is a bug but also I would like to ask about it.
When you use Arch.exe run "echo 'hello'" the Arch Linux instance is closed. I would like to prevent this closing because I'd like to do something like
Arch.exe run "echo 'hello'"
Arch.exe run "termite & && disown (pgrep termite) && exit"
That way I'd be starting directly my favorite terminal into my xming instace but keeping the Arch Linux instance running in background.
To Reproduce Using the run argument for Arch.exe produces an unexpected closure (in my opinion)
run
Arch.exe
Expected behavior I'd like to run a particular command but not closing Arch.exe after that execution.
Screenshots
Enviroment:
10.0.18363.778
wsl -l -v
wsl --help
appx
wsldl, version 20040300
Additional context Maybe this is an intenctional/wanted behaviour, but I would like at least to know how to prevent that closure.
The text was updated successfully, but these errors were encountered:
This issue will not be fixed.
You can prevent the close by devising the command line. e.g.
Arch.exe run "echo 'hello';bash"
Sorry, something went wrong.
No branches or pull requests
Describe the issue
I'm not sure if it is a bug but also I would like to ask about it.
When you use
Arch.exe run "echo 'hello'"
the Arch Linux instance is closed. I would like to prevent this closing because I'd like to do something likeArch.exe run "termite & && disown (pgrep termite) && exit"
That way I'd be starting directly my favorite terminal into my xming instace but keeping the Arch Linux instance running in background.
To Reproduce
Using the
run
argument forArch.exe
produces an unexpected closure (in my opinion)Expected behavior
I'd like to run a particular command but not closing Arch.exe after that execution.
Screenshots
![image](https://user-images.githubusercontent.com/4059108/81499742-069b9800-92ce-11ea-9d9c-81a994490249.png)
Enviroment:
10.0.18363.778
wsl -l -v
just shows the same thanwsl --help
so I guess the WSL1appx
but I don't remember right nowwsldl, version 20040300
Additional context
Maybe this is an intenctional/wanted behaviour, but I would like at least to know how to prevent that closure.
The text was updated successfully, but these errors were encountered: