From: Heribert Dahms <heribert_dahms@icon-gmbh.de>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: New sed in latest
Date: Fri, 02 Jun 2000 13:54:00 -0000 [thread overview]
Message-ID: <99B82AA9708ED0119B55006097125A00363EA9@ifk63.mach.uni-karlsruhe.de> (raw)
Hi Chris,
what about something like CYGWIN=force_binary for those who need it?
If you change od, I'd like that and/or --binary, since I routinely use
od -c to check for \r.
Do you have another suggestion how to find out (from e.g. bash) actual
line endings
present in input/output files or pipes for not (yet) text/binary smart
programs?
Bye, Heribert (heribert_dahms@icon-gmbh.de)
> -----Original Message-----
> From: Chris Faylor [SMTP:cgf@cygnus.com]
> Sent: Friday, June 02, 2000 20:24
> To: cygwin@sourceware.cygnus.com
> Subject: Re: New sed in latest
>
> On Fri, Jun 02, 2000 at 08:11:41PM +0200, Pierre.Humblet@eurecom.fr
> wrote:
> >On Thu, 1 Jun 2000 17:48:39 -0400, Chris Faylor <cgf@cygnus.com>
> wrote:
> >>You have my guarantee that when the cygwin mailing list is filled
> with
> >>the plaintive cries of people who are trying to process their binary
> >><snip>
> >
> >The current plaintive voices are about a textmode processing bug in
> the
> >dll. Masking that bug by making applications like sed ignore \r even
> >on binary mounted systems is only a reasonable TEMPORARY (band aid)
> >measure. Until now users mounting binary file systems had the
> >assurance that the tools would behave as on Unix. That was great, I
> >hope it will come back. Otherwise do you plan to keep on "fixing"
> more
> >applications? awk (for one) is also "broken" by \r\n :
> >
> >bash-2.04$ awk 'NF > 1' /u/hello.txt bash-2.04$ mount -b -f u:/ /u
> >bash-2.04$ awk 'NF > 1' /u/hello.txt hello bash-2.04$
> >
> >(hello.txt contains "hello \r\n")
>
> Yes. I plan on fixing more applications. In fact, awk is next on my
> list.
>
> This change was only partially motivated by the recent broken DLL. We
> have always had many many many complaints about "sed not working".
> The
> 1.1.1 DLL just aggravates the potential problems with binmode versus
> textmode processing. The problem won't go away when the DLL is fixed.
>
> You may have noticed that we've recently made similar modifications to
> ash and bash. I also expect that we will be making modifications to
> applications like 'od' which do not set binmode appropriately.
>
> Of course, the wonderful thing about all of this is that this is free
> software. You don't have to use it. Anyone can build their own
> version
> of sed which, theoretically, is able to process a binary file. It's
> not
> that hard at all.
>
> cgf
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-02 13:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-02 13:54 Heribert Dahms [this message]
2000-06-02 14:13 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2000-06-04 14:21 Christopher Jones
2000-06-04 15:27 ` Chris Faylor
2000-06-02 14:26 Heribert Dahms
2000-06-02 13:31 Earnie Boyd
2000-06-02 17:05 ` Bob McGowan
2000-06-03 1:52 ` Corinna Vinschen
2000-06-02 11:11 Pierre.Humblet
2000-06-02 11:23 ` Chris Faylor
2000-06-02 13:06 ` Charles Wilson
2000-06-02 13:24 ` Chris Faylor
2000-06-02 4:27 Peter Ring
2000-06-02 7:21 ` Corinna Vinschen
2000-06-01 13:52 Pierre.Humblet
2000-06-01 14:02 ` Chris Faylor
2000-06-01 14:09 ` Larry Hall (RFK Partners, Inc)
2000-06-01 14:49 ` Chris Faylor
2000-06-01 14:22 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99B82AA9708ED0119B55006097125A00363EA9@ifk63.mach.uni-karlsruhe.de \
--to=heribert_dahms@icon-gmbh.de \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).