ttjqryfbndgdx wrote:
Note that I don't have the issue with cat.
bash-3.2$ cat test1 > test2
bash-3.2$ xxd test2
000: 6161 610d 0a62 6262 0d0a aaa..bbb..
"cat" consider input and output as binary.
So the syntax "cat a > b" is always equivalent as "cp a b".
Now if you think t
Vincent Rivière freesbee.fr> writes:
>
> > I experienced the same issue with the "cat" command, and unfortunately I
> > didn't find any transparent solution
>
> However a non-transparent hack is to use first a text filter then pipe
> its output to the original command. The filter opens the f
I experienced the same issue with the "cat" command, and unfortunately I
didn't find any transparent solution :-(
However a non-transparent hack is to use first a text filter then pipe
its output to the original command. The filter opens the file in
textmode so it gets rid of the CR. Then, as
ttjqryfbndgdx wrote:
I know it's a common issue, but I didn't find a solution to my problem in the
archive.
I have a "dos" file (lines ends with carriage return+line feed : 0d0a in Hex) :
bash-3.2$ xxd test1
000: 6161 610d 0a62 6262 0d0a aaa..bbb..
If I apply a cygwin comman
I know it's a common issue, but I didn't find a solution to my problem in the
archive.
I have a "dos" file (lines ends with carriage return+line feed : 0d0a in Hex) :
bash-3.2$ xxd test1
000: 6161 610d 0a62 6262 0d0a aaa..bbb..
If I apply a cygwin command to this file, I get a
5 matches
Mail list logo
