Floris Lambrechts
Floris Lambrechts
This is long overdue, thanks for contributing this. If I find the time, I will review this and include it in the next release.
I agree that the --show output should go to `stdout`.
I suspect this is a bug caused by `search`/`replace` not using a proper regex replace, but a string replace. I don't think there's a known workaround at this point...
Related issue: #71.
Does this mean that all existing users will see spaces disappear in their config file? That would introduce a lot of unwanted diffs...
I agree that stripping the trailing whitespace is better. The question is, will all users be happy (or don't care) if we change this. Also, we have to decide if...
There is another complication: files which use multiple newline styles intermixed! When calling `open()` in text mode on a file, you can reference [newlines](https://docs.python.org/3/library/io.html#io.TextIOBase.newlines). Typically this is "\n" or "\r\n",...
Well it would be informative if you could share the error message of the failure :-) But I see you're using `end-of-file-fixer` which is known to cause problems. Please see...
To be honest, I knew this was an issue and would one day come up as a bug report... Sorry about that, and thanks for reporting it! My preference would...
Just found out about [os.linesep](https://docs.python.org/3/library/os.html#os.linesep) -- let's use that one to support as many platforms as possible.