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: igncr vs text mode mounts, performance vs compatibility

Hash: SHA1

According to Lewis Hyatt on 10/24/2006 12:57 PM:
> Just a thought, it would probably solve 99% of people's problems if you just
> specified that if the first line of the script ends in \r\n, then \r will be
> ignored for the rest of the file. Then you would just need to read the first
> line a byte at a time, and every subsequent line could be read efficiently
> whenever possible, right? And it seems unlikely that this could possibly break
> anything.

Propose a patch, and I will consider it.  In my opinion, it was much
easier to do igncr as an all or none option than it was to parse the first
line and discard \r on a per-file basis, not to mention that all-or-none
is easily configurable so that those of us who WANT literal \r as required
by POSIX can do so.  To date, I have been the only person proposing
patches in the area of \r\n handling, rather than just ideas (which is
probably why I am the maintainer of the cygwin bash port).  And I have no
personal interest in redoing this patch to a more complex algorithm at
this time.

- --
Life is short - so eat dessert first!

Eric Blake   
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -


Unsubscribe info:
Problem reports:

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