Gavin Sinclair wrote:
> Forget poisoned beer; you'll hang for this! :)  Anyway, once I muster up
> the courage to open cmd.exe, I'll try to reproduce it and fix it.  I guess
> you're using a Windows build of Ruby, which means the installer thinks
> it's producing files for a Windows vim.
> 
> Anyone else with similar troubles in a different Vim/Ruby/OS setup?

As someone mentioned, vim doesn't have trouble with \n even in Windows. 
So the easiest thing to do is just use unix style files. If anyone is 
masochistic enough to want to edit them with another editor, they can 
convert it to \n\r first with vim. :)

Or is win32 vim choking on startup with just \n?