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
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13469
Created by jflach on 2016-12-08 10:11:02 +00:00
Assignee: (none) Status: New Target Version: (none) Last Update: 2016-12-08 10:11:02 +00:00 (in Redmine)
Icinga Version: 2.6.0 Backport?: Not yet backported Include in Changelog: 1
Windows has special needs when it comes to escaping:
For a Programm to receive "foo bar" (with ") the correct shell escaped string would be "foo bar^", yet icinga creates the string "\"foo bar\"".
The text was updated successfully, but these errors were encountered:
Note:
I asked @LordHepipud to evaluate what's the right escaping algo.
My guess: Put a ^ before every character.
^
Sorry, something went wrong.
CreateProcess() seems not to parse the command line string, but to call the exe with that string and let it parse it by itself.
CreateProcess()
See http://www.daviddeley.com/autohotkey/parameters/parameters.htm
And here's how the exe parses the string: https://docs.microsoft.com/de-de/cpp/cpp/parsing-cpp-command-line-arguments?view=vs-2019
Fix Windows command escape for \"
c438910
refs #4849
115ecf8
Al2Klimov
Successfully merging a pull request may close this issue.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13469
Created by jflach on 2016-12-08 10:11:02 +00:00
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-12-08 10:11:02 +00:00 (in Redmine)
Windows has special needs when it comes to escaping:
For a Programm to receive "foo bar" (with ") the correct shell escaped string would be "foo bar^", yet icinga creates the string "\"foo bar\"".
The text was updated successfully, but these errors were encountered: