This is the mail archive of the
mailing list for the Cygwin project.
Re: Fwd: CRLF
- From: Andrew DeFaria <Andrew at DeFaria dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 01 Jan 2012 20:21:25 -0800
- Subject: Re: Fwd: CRLF
- References: <email@example.com> <firstname.lastname@example.org> <CAGHJv4cccBsX3=Mw3CykKXbyqZctONt0hUf6mUO_52RxsGXWemail@example.com> <CAGHJv4e2=c6Vm6Lu0W78rR1zVx7w1N_Ajs5Py+nfDnX1oRiCdg@mail.gmail.com> <Pine.BSM.4.64L.firstname.lastname@example.org> <CAGHJv4fgtM+QCFnrGb0pD-FT5A3R0hwOV8uF+4C_xEmtr_+dzQ@mail.gmail.com> <email@example.com> <20111231233109.GA3446@ednor.casa.cgf.cx> <firstname.lastname@example.org>
On 01/01/2012 12:45 AM, Franz Fehringer wrote:
Hi Christopher,Actually I hadn't heard about set -o igncr until this thread but
thinking about it I wouldn't use it. If I did then things would "just
work" for me. Problem is I'm very good with Cygwin but I come across
others who very often do not invest as much time to get to know Cygwin.
So if there's trailing CRs in a script I want it to fail so that I see
it. Otherwise another user will say "I tried that but it didn't work"
(as they always do) and I don't want it to "just work" when I try it - I
want it to fail like it most liked did for the other guy.
What is this "interesting workaround"?
Most probably we will use bash with "set -o igncr" btw.
When I hit this problem I simply do d2u <file> and I'm done.
Andrew DeFaria <http://defaria.com>
If people are good only because they fear punishment, and hope for
reward, then we are a sorry lot indeed.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple