backticks and $(...) aren't highlighted properly

[dimonomid]

Say, in this command:
vim $(find -name "something")
both vim and find should be highlighted as a command, but only vim is.

[anntzer]

There's also the process substitution commands, cmd <(cmd), cmd >(cmd) and cmd =(cmd).

[ZevEisenberg]

Also, commands in double-quoted strings. I was just bitten by this when I ran the following commit message:

git commit -m "Add library attributions Settings page that updates whenever `pod install` is run."

Of course, the pod install was executed, and the output was inserted into my commit message. I wouldn't have run into that problem if zsh-syntax-highlighting had flagged the backtics in the commit message.

[danielshahaf]

Also, commands in double-quoted strings.

Addressed by c3913e0 for the "$(…)" syntax.

[danielshahaf]

Summary:

What needs highlighting:

• Command substitution : echo foo``, : $(echo foo).
• Command substitution in double quotes: "`echo foo`", "$(echo foo)" — the latter case currently highlights the $ but not the nested command.
• Process substitution <(foo), =(foo), >(foo).

How to highlight:

• TBD. See Thoughts on recursive highlighting (inside backticks etc.) #389 for some thoughts on the matter.

[phy1729]

Also, commands in double-quoted strings.

And now addressed for backticks by f16e858. (Although back-quoted-argument is not highlighted by default).