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
in "foo", the rules for escaping quotes are awkward. You don't have to backslash-escape double quotes. (Unless of course they are within other double quote inside "foo", but the double-quotes on the outside of "foo" do not count towards the need-to-escape count.)
The text was updated successfully, but these errors were encountered:
This is slightly less silly after #8, i.e. there is now less reason to put quotes inside the shell command. But you still might do that, if you e.g. refer to an unchanging filename (a fixture, perhaps) which has a space in it. Unfortunately I still can't think of a way to change this that makes it significantly less silly.
In a pragma, when you say
in "foo", the rules for escaping quotes are awkward. You don't have to backslash-escape double quotes. (Unless of course they are within other double quote inside "foo", but the double-quotes on the outside of "foo" do not count towards the need-to-escape count.)
The text was updated successfully, but these errors were encountered: