Closed stasadev closed 1 month ago
Different but according to spec (hopefully). The exec key has been put into a shell until 0.25. Now the commandline is executed directly. Parsing is done as specified in the spec which states that arguments may be quoted as a whole using double quotes. So everything should work as expected. Correct me if I'm wrong.
Arguments may be quoted in whole. If an argument contains a reserved character the argument must be quoted. The rules for quoting of arguments is also applicable to the executable name or path of the executable program as provided.
Quoting must be done by enclosing the argument between double quotes and escaping the double quote character, backtick character, dollar sign ("$") and backslash character ("\") by preceding it with an additional backslash character. Implementations must undo quoting before expanding field codes and before passing the argument to the executable program. Reserved characters are space (" "), tab, newline, double quote, single quote ("'"), backslash character ("\"), greater-than sign (">"), less-than sign ("<"), tilde ("~"), vertical bar ("|"), ampersand ("&"), semicolon (";"), dollar sign ("$"), asterisk ("*"), question mark ("?"), hash mark ("#"), parenthesis ("(") and (")") and backtick character ("`").
Okay, thank you for the explanation.
I wasn't aware of these rules, and when it says MUST, I agree with that.
Package source
Official and AUR 0.26.0
App logs
Current Behavior
Something has changed in the way Albert reads
Exec
with single quotes inside.Create this desktop file, enable
Applications
plugin and runTest
inside Albert, it doesn't work because single quotes aren't handled like before:Expected Behavior
Albert 0.25.0 logs:
Anything else?
No response