Bowie Bailey wrote:
> Les Mikesell wrote:
>
>>On Tue, 2006-02-28 at 14:50, Robert Moskowitz wrote:
>>
>>>I have had some success (read no noticed problems), moving some
>>>text conf files from a Win <cr,lf> format to Linux and have them
>>>work. For example my zone files, moving them from my Win DNS
>>>server.
>>>
>>>But what about other files? I guess I want to know this more to
>>>prevent a mistake from crashing things, as I do have GEDIT.
>>>
>>>If I were to build an anaconda-ks.cfg in notepad, write it to a
>>>floppy then did a linux ks=floppy, would it work?
>>
>>I'm not sure there is a generic answer. Some things ignore the
>>CR's, some don't. It's always a good idea to remove them. On
>>Windows you can edit in wordpad instead of notepad and it will put
>>them back. If you edit in vim (either windows or Linux versions)
>>you can write either way with the:
>>
>>>set fileformat
>>
>>option.
>>
>>
>>>I have search the archives and google, but either I am missing the
>>>right search words, or something.
>>
>>In the old days with real vi, you would:
>>:%s/^v^m//
>>to get rid of them, but vim doesn't like that.
>
>
> It depends on how Vim recognizes the file. If Vim displays the file
> as a DOS file, it will hide the ^M and you can't search for it.
> If Vim displays the file as a unix file, it will show the ^M at the
> end of the line and you can search and replace it with the command
> shown above.
>
And failing that there's always dos2unix, or even:
$ tr -d '\015' < oldfile > newfile
IME the biggest problem with DOS-format files is with scripts run using
the '#!<interpreter>' syntax on the first line. Having extraneous CRs
at the end of such lines can just get you a "bad interpreter" error
message when you try to run the script.
James
