From: Andrey Repin <anrdaemon@yandex.ru>
To: "Andy Hall" <fixpertise-consulting@comcast.net>, cygwin@cygwin.com
Subject: Re: Join command fails to output fields on input file with DOS line endings.
Date: Tue, 23 Jul 2019 06:50:00 -0000 [thread overview]
Message-ID: <937822985.20190723094959@yandex.ru> (raw)
In-Reply-To: <009e01d540c6$c1b11d50$451357f0$@comcast.net>
Greetings, Andy Hall!
> This behavior of join surprised me:
> $ join -1 3 <(echo a b col3 c d | unix2dos) <(echo col3 f2 f3 f4 f5)
> f2 f3 f4 f5
> Join parses the input line well enough to execute the join, but the
> presence of the DOS line endings suppresses the
> output of fields from the first input.
> Compare with
> $ join -1 3 <(echo a b col3 c d) <(echo col3 f2 f3 f4 f5)
> col3 a b c d f2 f3 f4 f5
> which is correct.
> Here is a weirder example where the join field is missing and the output is reversed!
> NOK
> $ join <(echo col F1 | unix2dos) <(echo col F2)
> F2 F1
This makes perfect sense and actually explains what you see.
1. ("col", "F1\r") & ("col", "F2")
2. ("col", "F1\r", "F2")
3. printing "col F1\r F2"
4. obvious result: "col F1", then \r place cursor at the beginning of the
line, then " F2" overprints the line beginning.
5. observed result: " F2 F1"
> OK
> $ join <(echo col F1) <(echo col F2)
> col F1 F2
As Eliot said, don't do that.
--
With best regards,
Andrey Repin
Tuesday, July 23, 2019 9:45:05
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-07-23 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 19:50 Andy Hall
2019-07-22 19:58 ` Eliot Moss
2019-07-23 15:15 ` Andy Hall
2019-07-23 6:50 ` Andrey Repin [this message]
2019-07-23 12:18 ` Lemke, Michael ST/HZA-ZIC2
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=937822985.20190723094959@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=fixpertise-consulting@comcast.net \
/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).