-
Notifications
You must be signed in to change notification settings - Fork 32
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
Default syntax adds unexpected quotes #57
Comments
@Brice-xCIT can you show how you are passing the arguments? Each argument should be passed as a separate element to the arguments array. If you combine your arguments into one string, then the library thinks you are passing a single argument containing spaces, which must be escaped. |
@madelson Thank you for your reply. |
@Brice-xCIT interesting. Can you try calling it like this and seeing if that gets the expected result?
Note that I have If that doesn't work, can you post the exact code you're using to call MedallionShell for this command along with various things you've tried? Another thing to look into would be to try and make your call with the underlying |
@Brice-xCIT any update here? Did the above suggestion work for you? |
Closing for now; feel free to re-open if you still believe there is an issue. |
Hi there! Sorry for not answering earlier, I had to move on to more pressing work and could not get back to this. I still cannot really, so leaving this ticket closed is okay, I will come back to it later if I still have the issue. This said with your explanation I think I understand my mistake was to pass the 7th token split in 3 parts. Since I manage the escaping at a higher level I will keep my current solution for now. Thanks! |
Hello. I ran into an issue where I'm trying to execute a command with quotes:
but the default syntax added quotes in the inner command, making it fail on Ubuntu:
fortunately the options let me set up my own implementation of syntax (I am managing escaping myself) but the method is deprecated. Maybe it would be nice to un-deprecate it? :)
The text was updated successfully, but these errors were encountered: