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

When --case-replacements is used and files already have sequences like \E it does the wrong thing. #56

Closed
nevdelap opened this issue Jan 14, 2019 · 1 comment
Assignees
Labels
Milestone

Comments

@nevdelap
Copy link
Owner

Make it not change existing \E \T \U \L, etc when doing case replacements. I think it just needs to change them to something special, that should never exist in real life, as it does it. e.g. replace \E with '--ned--E--ned--' in the replacement string and subsequent case processing, or something.

@nevdelap
Copy link
Owner Author

Done.

@nevdelap nevdelap added the bug label Jan 19, 2019
@nevdelap nevdelap added this to the 1.2.5 milestone Jan 19, 2019
@nevdelap nevdelap self-assigned this Jan 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant