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

\xxxxx characters are escaped #719

Closed
joneff opened this issue Jun 10, 2019 · 1 comment
Closed

\xxxxx characters are escaped #719

joneff opened this issue Jun 10, 2019 · 1 comment

Comments

@joneff
Copy link

joneff commented Jun 10, 2019

There have been numerous reports #79, #345, #485.

While I do agree that semantically \1234 and are the same, it still makes a difference when we see the former in the output. My main concern is that private chars, like \f000 or \f0f0 are impossible to distinguish from one another when encoded ( vs ). That makes debugging and troubleshooting much harder.

I do understand the reasoning behind encoding, but shouldn't there be an option to disable it somehow?

I am also OK with using ugly hacks like #{unquote('\\') + f0f0} as long as I know that at some point those will not cease to work.

@nex3
Copy link
Contributor

nex3 commented Jun 11, 2019

Duplicate of #568

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

2 participants