public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Leonid Mironov <lvm@royal.net>
To: "cygwincygwin.com" <cygwin@cygwin.com>
Subject: issue when piping from a windows program
Date: Tue, 11 Apr 2023 09:15:03 +0200	[thread overview]
Message-ID: <trinity-bed8517a-5458-4f9d-8ee1-6d6698fcdea7-1681197303539@3c-app-mailcom-lxa08> (raw)

I am trying to feed the output of wmic.exe - a windows console program, to cygwin bash script. 
wmic.exe produces UTF16LE output with BOM and CR/LFs, so I am using dos2unix to convert it. 
The problem is that when I write wmic.exe output to a file and then use dos2unix to convert this file 
I get the expected result - ASCII file with LFs, I get the same result when I pipe this file to dos2unix, 
but when I pipe wmic.exe output directly to dos2unix I get ASCII file with CR/LFs and an extra empty line. 
Cygwin is up to date, windows 10. What gives?

Here are the hexdumps

of 'wmic /NAMESPACE:\\\\root\\WMI PATH BatteryStatus get charging,voltage,remainingcapacity,chargerate>file'

00000000  ff fe 43 00 68 00 61 00  72 00 67 00 65 00 52 00  |..C.h.a.r.g.e.R.|
00000010  61 00 74 00 65 00 20 00  20 00 43 00 68 00 61 00  |a.t.e. . .C.h.a.|
00000020  72 00 67 00 69 00 6e 00  67 00 20 00 20 00 52 00  |r.g.i.n.g. . .R.|
00000030  65 00 6d 00 61 00 69 00  6e 00 69 00 6e 00 67 00  |e.m.a.i.n.i.n.g.|
00000040  43 00 61 00 70 00 61 00  63 00 69 00 74 00 79 00  |C.a.p.a.c.i.t.y.|
00000050  20 00 20 00 56 00 6f 00  6c 00 74 00 61 00 67 00  | . .V.o.l.t.a.g.|
00000060  65 00 20 00 20 00 0d 00  0a 00 30 00 20 00 20 00  |e. . .....0. . .|
00000070  20 00 20 00 20 00 20 00  20 00 20 00 20 00 20 00  | . . . . . . . .|
00000080  20 00 46 00 41 00 4c 00  53 00 45 00 20 00 20 00  | .F.A.L.S.E. . .|
00000090  20 00 20 00 20 00 33 00  37 00 37 00 33 00 34 00  | . . .3.7.7.3.4.|
000000a0  20 00 20 00 20 00 20 00  20 00 20 00 20 00 20 00  | . . . . . . . .|
000000b0  20 00 20 00 20 00 20 00  20 00 20 00 31 00 32 00  | . . . . . .1.2.|
000000c0  37 00 34 00 30 00 20 00  20 00 20 00 20 00 0d 00  |7.4.0. . . . ...|
000000d0  0a 00                                             |..|
000000d2

of wimic>file followed by dos2unix<file or cat file|dos2unix

00000000  43 68 61 72 67 65 52 61  74 65 20 20 43 68 61 72  |ChargeRate  Char|
00000010  67 69 6e 67 20 20 52 65  6d 61 69 6e 69 6e 67 43  |ging  RemainingC|
00000020  61 70 61 63 69 74 79 20  20 56 6f 6c 74 61 67 65  |apacity  Voltage|
00000030  20 20 0a 30 20 20 20 20  20 20 20 20 20 20 20 46  |  .0           F|                                                              
00000040  41 4c 53 45 20 20 20 20  20 33 37 37 33 34 20 20  |ALSE     37734  |                                                              
00000050  20 20 20 20 20 20 20 20  20 20 20 20 31 32 37 34  |            1274|
00000060  30 20 20 20 20 0a                                 |0    .|
00000066

and of wimic|dos2unix

00000000  43 68 61 72 67 65 52 61  74 65 20 20 43 68 61 72  |ChargeRate  Char|
00000010  67 69 6e 67 20 20 52 65  6d 61 69 6e 69 6e 67 43  |ging  RemainingC|
00000020  61 70 61 63 69 74 79 20  20 56 6f 6c 74 61 67 65  |apacity  Voltage|
00000030  20 20 0d 0a 30 20 20 20  20 20 20 20 20 20 20 20  |  ..0           |
00000040  46 41 4c 53 45 20 20 20  20 20 33 37 37 33 34 20  |FALSE     37734 |
00000050  20 20 20 20 20 20 20 20  20 20 20 20 20 31 32 37  |             127|
00000060  34 30 20 20 20 20 0d 0a  0d 0a                    |40    ....|
0000006a

 
 

             reply	other threads:[~2023-04-11  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  7:15 Leonid Mironov [this message]
2023-04-11  9:02 ` Marco Atzeri
2023-04-11 14:43 ` Andrey Repin
2023-04-12  7:02   ` Brian Inglis
2023-04-12  8:56 ` Takashi Yano

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=trinity-bed8517a-5458-4f9d-8ee1-6d6698fcdea7-1681197303539@3c-app-mailcom-lxa08 \
    --to=lvm@royal.net \
    --cc=cygwin@cygwin.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).