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
Escape single quotes in commands? #89
Comments
This is a bug, I'll handle an update shortly. |
I did install from master, saw the new version come in, and it doesn't fly:
|
Looking at this more carefully I think there's some confusion. This is my sample input:
That works 100%. No quoting involved. Adding quotes around the sed-input causes failure:
In both cases the error is from sed, which looks like this:
i.e. The issue here is that the command is being taken with the quotes literally, because we're not runnign with a shell. So I think the immediate problem you have is solved by dropping the quotes. The second problem is caused by not running with bash. I think that can be solved by adding a needless redirect:
That's because the way that I run shell commands depends on whether there is a redirection, or similar "complex" thing present. I hope that one/other of those solves things for you. But I guess I'll leave this open and see if I can add:
To force the use of the shell, rather than the hack with the redirection character. |
OK I see it work as you say, and this is nice I don't want to deal with escaping.
|
Good comments. I'll create issues for the missing features you suggest. For editing I've done a hack which is to use the edit-module twice;
Doesn't work generally, such as changing the port of sshd, but it can work in emergencies. I can see this working, and being easy to add:
|
No matter how I try to escape, I can't do:
The text was updated successfully, but these errors were encountered: