You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hm... I had at the begining problems to understand why
output+="$(printf "%02x,""'${string:i:1}")"
is correct.
But know I think I got it... $(...) executes the internal parts inside brackets and there an own context is available, so printf "%02x," "'${string:i:1}" is interpreted by bash correct.
This will be tricky to parse, so it will take some time to implement. In the mean while you could turn off validations in preferences if it bothers you too much.
de-jcup
changed the title
Syntax Error
Syntax Error - highlighting and parse of quotation marks not correct interpreted when inisde execution part
Feb 20, 2021
de-jcup
changed the title
Syntax Error - highlighting and parse of quotation marks not correct interpreted when inisde execution part
Syntax Error - highlighting and parse of quotation marks not correct interpreted when inside execution part
Feb 20, 2021
#!/usr/bin/env bash
string_to_asciihex() {
local string="$1"
local -i i eos
local output=""
}
The text was updated successfully, but these errors were encountered: