[*] Use “$@” with quotes: prog=”$1″ “$@” ecode=”$?” echo “$prog exited with $ecode” This will pass each argument exactly as it was received. If you don’t include the quotes, each element will be split according to $IFS: “$@” is like “$1” “$2” “$3” …, passing each element as a separate argument. “$*” is like “$1 … Read more
When calling from cmd.exe, things get tricky; here’s a simplified example: powershell -c “ffmpeg.exe -h “^””User-Agent: usra`r`nCookies: parm=a=1&b=2; session=1″^””” In short: From cmd.exe / batch files, to pass what PowerShell’s CLI should see as a double-quoted argument inside an overall “…” string passed to -Command (-c): In Windows PowerShell (powershell.exe): use “^””…”^”” (sic) In PowerShell … Read more
For detailed and very useful background, see the answer by mklement0 After much frustration, I have decided to list all variants of quote escaping that I’ve tried, and came up with one more, which suddenly worked! So, sharing it here: kubectl patch deployment wapi-backend-d1 –patch ‘{\”spec\”: {\”template\”: {\”metadata\”: {\”labels\”: {\”date\”: \”test123\”}}}}}’ This is how to … Read more
You are better off using a program like jq to generate the JSON, if you don’t know ahead of time if the contents of the variables are properly escaped for inclusion in JSON. Otherwise, you will just end up with invalid JSON for your trouble. BUCKET_NAME=testbucket OBJECT_NAME=testworkflow-2.0.1.jar TARGET_LOCATION=/opt/test/testworkflow-2.0.1.jar JSON_STRING=$( jq -n \ –arg bn “$BUCKET_NAME” … Read more
The reason this happens is because of the order in which the shell parses the command line: it parses (and removes) quotes and escapes, then replaces variable values. By the time $test gets replaced with One “This is two” Three, it’s too late for the quotes to have their intended effect. The simple (but dangerous) … Read more
In all of the cases above, the variable is correctly set, but not correctly read! The right way is to use double quotes when referencing: echo “$var” This gives the expected value in all the examples given. Always quote variable references! Why? When a variable is unquoted, it will: Undergo field splitting where the value … Read more
Single quoted strings will not expand variables in PowerShell. Try a double quoted string e.g.: “$computer\admin”
Try using the –% operator to put PowerShell into simple (dumb) argument parsing mode: curl.exe –% -ku user@email:mypass -X PUT -d “data={\”password\”:\”keypass\”}” https://build.phonegap.com/api/v1/key This is quite often useful for invoking exes with argument syntax that runs afoul of PowerShell’s argument syntax. This does require PowerShell V3 or higher.
If you really want to use single quotes in the outermost layer, remember that you can glue both kinds of quotation. Example: alias rxvt=”urxvt -fg “”‘”‘#111111′”‘”‘ -bg ‘”‘”‘#111111′”‘” # ^^^^^ ^^^^^ ^^^^^ ^^^^ # 12345 12345 12345 1234 Explanation of how ‘”‘”‘ is interpreted as just ‘: ‘ End first quotation which uses single quotes. … Read more
Why When the string is expanded, it is split into words, but it is not re-evaluated to find special characters such as quotes or dollar signs or … This is the way the shell has ‘always’ behaved, since the Bourne shell back in 1978 or thereabouts. Fix In bash, use an array to hold the … Read more