Ah that Windows. Someone should incorporate dos2unix conversion as an standard step in some of the make/config process.

On the contrary - something like this should not happen behind the user's back, considering the platform where configure scripts are built can be different from the target platform.

I'd also love to teach vim how sto how those pesky ^M characters. It doesn't, and that's perceived user-friendliness gone too far. Proper vi on Unix does the right thing.

On Fri, Jul 08, 2011 at 11:40:27PM +0100, Lars Hecking wrote:

I'd also love to teach vim how sto how those pesky ^M characters. It doesn't, and that's perceived user-friendliness gone too far. Proper vi on Unix does the right thing.

If it thinks it's a DOS format file then it normally puts [dos] on the status line.

You can change the autodetection at load time, or change file format at edit time or...

http://vim.wikia.com/wiki/File_format

On 7/8/2011 4:40 PM, Lars Hecking wrote:

I'd also love to teach vim how sto how those pesky ^M characters.

It does, when the line ending style is mixed.

When the line ending style is consistent, you can make Vim show the file type in the status line by adding something like this to your .vimrc:

set laststatus=2 set statusline=%F\ %m%r%h%w%y\ [%{&ff}]\ [%l,%v]\ [%p%% of %L lines]

The important bit is the %{&ff}: that will be "dos", "mac" or "unix". The brackets around it are decorations only. Adjust to taste.