> I have no comment on the EOF character CTRL+Z (from a quick google, > ascii 26?). I didn't even know that existed, and don't care how that > is handled. Most text files dont have a trailing CTRL+Z from what I've > seen.
It's from old systems, you might call it exotic. That's why showing it could be useful, it will only show rarely and probably help the user notice there is something strange going on. > As far as adding 'noeol' to 'fillchars', here is the problem: Vim does > not keep track of the eol status as the file is edited. It only checks > it once upon file open. Simply open up a noeol file, use `:set eol?` > and you'll see 'noendofline', edit the file, save it, Vim auto adds > the eol, then use `:set eol?` again and Vim will incorrectly report > noeol still, even though it was changed and added. I believe Vim needs > to keep track of the original eol state of the file, so that it can > determine what to do for the existing 'fixeol/nofixeol' setting, and > so that shouldn't be changed either I guess Please use a separate issue for separate things. We are discussing the visibility of the state in this issue. If you find a repro case where the value of 'endofline' is wrong, please create a new issue for that. Otherwise we get things mixed up or forgotten, closing the issue when it is only partly fixed. I will not act on this remark now, please use another issue for that. > If the 'eol' listchar cannot be changed for backwards compatibility > with Vi, thats fine. My point is that then there is no visual way > inside Vim to consistently display \n (LF) chars. And the only way to > display \r (CR) is to set ff=unix and then you will see `^M` > displayed. Non printable characters like LF/NL/CR are of course not visible. Only in some cases we do indicate they exist in some way. But LF/NL is a line break, not something you see in pixels. I see no reason at all to make it visible, other then the mentioned list mode character. The CR showing up as ^M is also from old times, and I don't see a need to change that. > It just seems like the easiest and most non intrusive solution is to > simply add CR and LF options to listchars and then people can visually > see this data, independent of the chosen fileformat I do not understand what you mean with "see this data", you don't say what you actually imagine would show up. And really I don't see any need for it yet. You'll have to come with more convincing arguments. Saying "independent of the chosen fileformat" is wrong, we do want to show the actual state, not some decoration. Users should be aware of what's going to be written and avoid having options to create confusion. Keep in mind that users will be concentrating on the text, and the fileformat is a setting that only matters when reading and writing the buffer. Not something you need constant reminding of, more distracting than useful. -- Despite the cost of living, have you noticed how it remains so popular? /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// \\\ \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20221110182218.8A9E81C108B%40moolenaar.net.
