Open jamesls opened 8 years ago
Was this ever resolved? @jamesls
@HipsterZipster Nope, still an issue as of today
This seems to do with how newline characters in Windows are handled in VIM.
From DOS vs. Unix Line Endings:
DOS/Windows uses a Carriage Return + Line Feed (
<CR><LR>
) (\r\n
) Unix/Linux just uses a Line Feed (<LR>
) (\n
)
From How Is Newline Handled in Python and Various Editors?:
When you use
e ++ff=unix3
to force Vim to treat this file as a unix file. Vim will then treat the\n
characters as newline, thus removing it from the buffer. But the\r
characters in the file will now be treated as normal characters and will be shown as^M
When generating docs on windows, newlines are rendered as '^M'. Need to track down where this
\r\n
behavior is being introduced.