On 2007-08-02, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > Charles E Campbell Jr wrote: > > Hello! > > > > I just got a request from a vimball user: > > > > --------------------------------------------------------------------------------------------- > > - vim copes with unix scripts on windows, but not with windows scripts > > on unix. Hence the standard recommendation to use "unix" for the > > 'fileformat' option when writing plugins (:help script|/fileformat/). > > Unfortunately, vimball seems to produce "dos" 'fileformat' on > > windows, which results in chaos when trying to unpack on unix. > > > > Could vimball please produce "unix" 'fileformat', on all platforms? > > --------------------------------------------------------------------------------------------- > > > > Does anyone foresee any problems with setting (locally) ff=unix ?
No. In fact, Cygwin's vim chokes on config files with DOS line endings, so I have to remember to 'd2u' all the files I un-vimball on a Windows machine before running vim again. > I don't know what Steve Hall does nowadays, but when I was on Windows, I used > _unix_ sources (plus extra plus lang), and unix-like fileformat for both > sources and runtimes. I never had any problem running unix-format scripts on > Windows. Neither have I. > A few caveats: > - Notepad chokes on Unix-format text files; but both Vim and WordPad (among > others) can edit them with no problem. Again, for Vim this requires "unix" as > part of 'fileformats', which is the 'nocompatible' default. WordPad can open and edit files with Unix line endings, but it always saves files in DOS format, so you should never use it to edit files that must remain in Unix format. Regards, Gary --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
