This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: updated bash to latest 3.1.17(8)-release; startup has errors now

On Tue, 3 Oct 2006, Larry Hall (Cygwin) wrote:

> On 10/03/2006, DePriest, Jason R. wrote:
> <snip>
> > vi did not show any unusual line endings (CR/LF) in /etc/profile
> > before I sent my message in
> vi/vim will only show you the CR/LF if you tell it to.  So if you're
> not looking for them, vi/vim may have hidden them from you.  You may
> want to try 'od -c' on the file(s) in question.

Since many people mentioned that they opened the files in question in vim
and did not see unusual line endings, here's some non-Cygwin-specific, but
relevant, vim info:

By default, when vim loads the file in which *all* line endings are CR/LF,
it will display the file normally, but show "[dos]" in the status line.
It's easy to miss if you're not watching for it.  That property can also
be queried using "set fileformat?".

This behavior can be turned off globally by "set fileformats=unix".

Alternatively, "vi -b myfile" will open myfile in binary mode, and will
display all CR/LF line endings.
      |\      _,,,---,,_ |
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]