From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Leonid Mironov <lvm@royal.net>
Subject: Re: issue when piping from a windows program
Date: Wed, 12 Apr 2023 01:02:49 -0600 [thread overview]
Message-ID: <9854bbe6-aa59-6117-0d48-522684031f28@Shaw.ca> (raw)
In-Reply-To: <1138153048.20230411174322@yandex.ru>
On 2023-04-11 08:43, Andrey Repin via Cygwin wrote:
> Greetings, Leonid Mironov!
>
>> 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?
>
> You don't need d2u. Use `… | iconv -f UTF16LE | tr -d '\r'`
> (Don't even need -t for iconv - it assumes current locale settings as
> default source/destination encoding.)
d2u -ul converts from utf-16le to utf-8
When I run wmic under mintty or | less it looks fine to me e.g.:
$ wmic baseboard list full | less # optional
but the output could benefut from \r stripping:
$ wmic baseboard list full | tr -d '\r' | cat -A | less
https://learn.microsoft.com/en-us/windows/whats-new/deprecated-features#deprecated-features
The WMIC tool is deprecated in Windows 10, version 21H1 and the 21H1 General
Availability Channel release of Windows Server. This tool is superseded by
Windows PowerShell for WMI.
https://learn.microsoft.com/en-us/powershell/scripting/learn/ps101/07-working-with-wmi
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-04-12 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 7:15 Leonid Mironov
2023-04-11 9:02 ` Marco Atzeri
2023-04-11 14:43 ` Andrey Repin
2023-04-12 7:02 ` Brian Inglis [this message]
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=9854bbe6-aa59-6117-0d48-522684031f28@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.com \
--cc=lvm@royal.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).