RE: indent.exe strangeness

[BMetzenthen at cochlear dot com dot au]

Bingo!  That was the problem.  Thanks.

I was using /cygdrive/..., which are binmode.

Mounting the win directories under the cygwin heirarchy in text mode solved
that little problem.

I operate cygwin the same way as I use Linux, ignoring binmode/textmode
until it bites me (usually, this means ^M characters appear at line
endings, not in the middle of lines).  I assume that the appropriate thing
to do here would be to patch the indent sources to make it work as expected
when using binary mounted directories.

Bill


                                                                                                                 
                    Kevin Schnitzius                                                                             
                    <kevin.schnitzius@c        To:     "'BMetzenthen@cochlear.com.au'"                           
                    itrix.com>                 <BMetzenthen@cochlear.com.au>, cygwin@cygwin.com                  
                                               cc:                                                               
                    15/11/2001 14:05           Subject:     RE: indent.exe strangeness                           
                                                                                                                 
                                                                                                                 




Are your source drives mounted as binary or text?

Kevin

 -----Original Message-----
From:           BMetzenthen@cochlear.com.au
[mailto:BMetzenthen@cochlear.com.au]
Sent:           Wednesday, November 14, 2001 21:58
To:        cygwin@cygwin.com
Subject:        indent.exe strangeness

I've tried a few approaches with obtaining (or building) indent.exe but the
executable always seems to include extra ^M characters (usually following
the whitespace which is inserted at the start of lines) to the beautified
output.

Does anyone know if this is:
(a) a run-time configuration problem,
(b) a corrupted/out-of-date dll, or
(c) a known bug with indent?


Bill

============================================================================

==========

"The information contained in this e-mail message may be confidential
information, and may also be privileged. If you are not the intended
recipient, any use, interference with, disclosure or copying of this
material is unauthorised and prohibited.  If you have received this message
in error, please notify us by return email and delete the original
message."

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/




======================================================================================

"The information contained in this e-mail message may be confidential information, and may also be privileged. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited.  If you have received this message in error, please notify us by return email and delete the original message."

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/