Timeline for How to highlight windows end of line characters aka ^M, \r\n?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2016 at 13:40 | history | edited | d.k | CC BY-SA 3.0 |
the answer has been updated with the reason why it was unaccepted (it does not work in certain contitions)
|
| Jan 21, 2016 at 8:49 | vote | accept | d.k | ||
| Jul 26, 2016 at 13:38 | |||||
| Jan 19, 2016 at 15:03 | comment | added | d.k | @jamessan, I actually don't know what can I put into the status line, in this case, I'm very new to vim. I just always work with "unix" files, but sometimes it can happen that windows eols are used (which is not proper in my environment) by someone else, so I wanted a way to spot such situations immediately. | |
| Jan 19, 2016 at 14:39 | comment | added | jamessan |
Ah, so you're specifically setting 'ffs' in such a way that Vim will never detect a file as having dos line endings, so that you can highlight them? Why not just put something in your statusline to show what the fileformat is, so you know when it's dos vs. unix?
|
|
| Jan 19, 2016 at 6:54 | comment | added | d.k |
@jamessan, do you mean a file which is edited in vim without the ffs option set to unix? Right now I checked a file, which had only windows eol (that is no mix) and everything was highlighted fine. I suppose that the ffs option is relevant here, because only with it I have managed to show carriage return characters.
|
|
| Jan 18, 2016 at 19:37 | comment | added | jamessan | Note that this will only ever match something if the file has mixed line endings. | |
| Jan 18, 2016 at 16:47 | history | answered | d.k | CC BY-SA 3.0 |