> On 7/22/2019 12:59 PM, Eliot Moss wrote:
> On 7/22/2019 12:50 PM, Andy Hall wrote:
> > 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
>
On July 22, 2019 9:51 PM Andy Hall wrote:
>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
See if this reduces your surprise somewhat:
$ join -1 3 <(echo a b col3 c d | unix2dos) <(echo col3 f2 f3 f4 f5) | cat -A
--
Pro
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
On 7/22/2019 3:50 PM, Andy Hall wrote:
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 fr
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
5 matches
Mail list logo