Windows doc gens show ^M chars

[jamesls]

When generating docs on windows, newlines are rendered as '^M'. Need to track down where this \r\n behavior is being introduced.

[HipsterZipster]

Was this ever resolved? @jamesls

[Kittzus]

@HipsterZipster Nope, still an issue as of today

[KyleMit]

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

See Also

• What is ^M and how do I get rid of it?
• How do I hide the eol doc chars ^M in VIM
• Vi on Linux: show ^M line endings for DOS-format files