http://bugs.winehq.org/show_bug.cgi?id=21131
--- Comment #15 from Frédéric Delanoy frederic.delanoy@gmail.com 2011-10-03 01:39:07 CDT --- (In reply to comment #14) As a start, Martin Wilck has just sent some cmd /c parsing fixes (not yet applied); see wine-devel for information.
This bug is not limited to "&", should I submit a separate bug report?
wine cmd /c echo "!" bash: !: event not found
As mentioned in the message, bash interprets the bang, not wine. Use '!' instrad (i.e. use bash quoting rules). To check wine behaviour more closely, you should preferably try them from within "wine cmd" (mixing wine/cmd quoting can be tricky; e.g. ./wine cmd echo '"!"')
wine cmd /c echo "<" Path not found
wine cmd /c echo ">" Path not found
wine cmd /c echo ""
[must use Ctrl+c to get out, else it keeps giving you a ">"]
wine cmd /c echo "|" Echo is ON
wine cmd /c echo "`"
[must use Ctrl+c to get out, else it keeps giving you a ">"]
wine cmd /c echo """
[must use Ctrl+c to get out, else it keeps giving you a ">"]
Those work with Martin's patches applied, tried within cmd
Hopefully they'll be merged soon.