This is slightly off-topic, but do people actually work at a place where someone would get upset about adding a single invisible character with no negative impact on anything at all to the end of a file, when the file is being changed already anyway? I work at a company with a fairly strict change management process and nobody has ever complained to me about adding a newline to the end of a DOS- format file (or even about changing a mixed-format DOS/Unix file into a strictly Unix or strictly DOS file). In code review, the reviewer simply notices "oh, I guess nothing changed on that line" and if they don't know what happened may think it's strange but nothing a simple "hey, what did you do here?" can't fix. Hell, even adding to the commit comment (you do use those, right?) something like "...and added a newline to the end of the file" can tell the reviewer what happened with no questions needed.
That said, I'm not really sure why the 'eol' option has no effect unless you're in binary mode. I cannot think of a good reason for this to be the case, unless it's just the "it's how vi did it" argument. -- You received this message from the "vim_use" 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
