Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make quoting rules less silly #1

Open
cpressey opened this issue Jan 3, 2015 · 1 comment
Open

Make quoting rules less silly #1

cpressey opened this issue Jan 3, 2015 · 1 comment

Comments

@cpressey
Copy link
Member

cpressey commented Jan 3, 2015

In a pragma, when you say

...is implemented by shell command "foo"

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.)

@cpressey
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant