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
Feature: Add an option to bypass shell wrapper #80
Comments
Hi! Thanks for your really accurate bug report. The shell detection is adding an extra 'powershell core' process, and the indirection makes it a quotation hell syntax. Let me give you a shamefull workaround. Try:
or without the cmd, you need to escape the
or an example with variable substitutions:
I agree. It would imply that the command to run be something that can be executed by I'm unsure on how to name the 'feature', or what letter to assign to it (as in |
Hi @r-darwish, this will be released in v1.0. An early draft pre-release is open for testing in case you want to try it. |
Issue Description
Due to gsudo's shell detection, trying to run a command with the Windows Powershell from Powershell Core will cause gsudo to run Powershell Core first. It would be useful if we can have a flag to disable the shell detection.
Steps to Reproduce
Run the following command from Powershell core:
Screenshots
Context:
The text was updated successfully, but these errors were encountered: