Hi, > If you use git, then in “git help attributes” the example mentioning *.vcproj > files might be useful for you. Possibly the end-of-line normalization > offered > by git includes the case where just the last line needs normalization.
Roland - thank you, I did not know about that feature of git, it might be useful for my *.csproj situation, but generally I don't want my files to be normalized in any way, I want them to be left intact. > 1. 'norespecteol' (default) means that an EOL is always added unless > 'eol' + 'bin' are set, i.e. Vim's existing behavior. > 2. Opening an existing file when 'respecteol' is set honors the current > state of the EOL on the last line, and should set 'eol' accordingly. > 3. If a user wishes a new, unsaved buffer to not have an EOL on the last > line, she can set 'respecteol' and 'noeol'. James - I think in #1 you meant 'noeol' + 'bin' - if yes, then 1-3 is exactly what my patch adds. > I believe the final EOL in a file should be made visible and > editable. Olaf - James is right, according to the POSIX standard, EOL means EOL, not 'newline', regardless of how it's treated by some other text editors. Besides, I don't want to break the existing Vim functionality, I just want to expand the horizons of its usage beyond the Unix world it has been originally created for. -- Best Regards, Pavel -- -- 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]. For more options, visit https://groups.google.com/d/optout.
