On Thu, 10 Jan 2002, Charles Albrecht wrote:
> In Chris' example, I think vim used Mac or DOS line endings rather
> than unix ones, most likely based on its fileformats settings,
Bingo!
[localhost Thu 10:54:29am ~]% grep ' ff' ~/.vimrc
"set ff=unix
set ffs=dos,unix,mac
[localhost Thu 10:54:37am ~]%
I'd originally created this .vimrc file when I installed [G]vim on NT,
and wanted to be able to work on the same documents locally, on the OSX
box, or on the Linux servers without complaints about line endings or
having Notepad garble a nicely formatted document or Pico throw in lots
of ^M characters or what have you. I've been copying the same config file
from system to system without really thinking about it since then, but
obviously that was indeed the problem here, and last night I commented
out the offending line & resolved the problem.
Still though, I'm really confused by the line endings issue on OSX. It
seems like a lot of programs -- low level BSD stuff and high level Mac
stuff alike -- have to either become consistent or agnostic in the way
they handle line endings, and I'm not at all sure what the best way to
resolve this is on a general level. Inheriting two more or less opposite
conventions has been making things way too messy...
--
Chris Devers [EMAIL PROTECTED]
Apache / mod_perl / http://homepage.mac.com/chdevers/resume/
