Render Line Endings
This extension shows end-of-line characters (CR, LF, or CRLF) when whitespace rendering is turned on. Additionally, it can mark all non-default line endings in a different color. It can be also configured to show trailing whitespace characters as errors.
Since the extension only renders visible portion of text, it's fast, even for huge documents.
It fully supports language-specific EOL and whitespace settings.
If whitespace rendering is turned on, you will see the symbol for either LF
Works well with
Supports rendering of only the selection (
Supports highlighting of non-default EOL - even with the language-specific
Supports highlighting of training whitespace (
Whether extension is decorating or not is handled by
This extension contributes the following settings (compatible with
Color is taken from
Default line ending is determined based on
Atom Style Configuration
Mark Non-Default Line Ending
Mark Extra Whitespace
Place Decorations Before EOL Instead of After
Mixed Line Endings Are Not Supported
Visual Studio Code normalizes the line endings upon load and thus this extension will only show one kind of line ending character. Currently it is not possible to have multiple different line endings (see issue 127).
CR Line Ending Is Not Supported
Visual Studio does not support CR line ending (see issue 35797). Therefore, while you can configure it, you will never see CR as a line ending.
Not Rendering Glyphs For Large Files
For performance reasons Visual Studio Code doesn't synchronize files that are
over 5MB in size (see issue 27100).
Therefore, no line-ending characters will be visible on large files. To avoid
this you can set
Slow Update For Large Files
This extension doesn't process the whole file but just a visible portion so it's highly unlikely it will be the cause. I recommend disabling each extension in turn to determine which extension is causing the issue.
Conflict with GitLens
This extension might be in conflict with other extensions providing their information as end of the line decorations, the most notable example being GitLens. This is due to [issue #33852](https://github.com/microsoft/vscode/issues/33852) and it cannot be solved at this moment.
As a workaround you can try setting