From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygcheck and literal plus sign
Date: Sat, 28 Jan 2017 17:45:00 -0000 [thread overview]
Message-ID: <a8ddccfc-6eed-0d05-b756-f95d7e5ccdf2@SystematicSw.ab.ca> (raw)
In-Reply-To: <588c8cc9.a5249d0a.d8d5b.49c2@mx.google.com>
On 2017-01-28 05:21, Steven Penny wrote:
> On Fri, 27 Jan 2017 21:01:14, Doug Henderson wrote:
>> Try this:
>> $ cygcheck -p "mingw32-g[*-,][*-,]"
>> Found 4 matches for mingw32-g[*-,][*-,]
> Thanks for this. Using ranges is gross, because it relies on your locale, but
> it did put me on the right track:
> $ cygcheck -p 'mingw32-g[:punct:][:punct:]' | awk 'NR>1{$0=$1}1'
> Found 8 matches for mingw32-g[:punct:][:punct:]
> mingw64-i686-gcc-core-5.4.0-2
> mingw64-i686-gcc-core-5.4.0-3
> mingw64-i686-gcc-debuginfo-5.4.0-2
> mingw64-i686-gcc-debuginfo-5.4.0-3
> mingw64-x86_64-gcc-core-5.4.0-2
> mingw64-x86_64-gcc-core-5.4.0-3
> mingw64-x86_64-gcc-debuginfo-5.4.0-2
> mingw64-x86_64-gcc-debuginfo-5.4.0-3
Your command is the same as:
$ cygcheck -p mingw32-g[:ctnpu][:ctnpu] | sed '2,$s/\s.*//'
Found 8 matches for mingw32-g[:ctnpu][:ctnpu]
mingw64-i686-gcc-core-5.4.0-2
mingw64-i686-gcc-core-5.4.0-3
mingw64-i686-gcc-debuginfo-5.4.0-2
mingw64-i686-gcc-debuginfo-5.4.0-3
mingw64-x86_64-gcc-core-5.4.0-2
mingw64-x86_64-gcc-core-5.4.0-3
mingw64-x86_64-gcc-debuginfo-5.4.0-2
mingw64-x86_64-gcc-debuginfo-5.4.0-3
ITYM:
$ cygcheck -p mingw32-g[[:punct:]][[:punct:]] | sed '2,$s/\s.*//'
Found 4 matches for mingw32-g[[:punct:]][[:punct:]]
mingw64-i686-gcc-g++-5.4.0-2
mingw64-i686-gcc-g++-5.4.0-3
mingw64-x86_64-gcc-g++-5.4.0-2
mingw64-x86_64-gcc-g++-5.4.0-3
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2017-01-28 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 23:59 Steven Penny
2014-01-22 5:58 ` Christopher Faylor
2014-01-22 6:46 ` Marco Atzeri
2014-01-22 11:35 ` Andrew Schulman
2014-01-22 15:07 ` Christopher Faylor
2014-01-22 16:03 ` Andrew Schulman
2014-01-22 16:06 ` David Boyce
2014-01-22 16:13 ` Larry Hall (Cygwin)
2014-01-25 2:26 ` Steven Penny
2014-01-27 15:48 ` Gates, Roger
2014-01-27 18:59 ` Larry Hall (Cygwin)
2014-01-27 22:43 ` Steven Penny
2017-01-28 3:01 ` Steven Penny
2017-01-28 4:01 ` Doug Henderson
2017-01-28 12:21 ` Steven Penny
2017-01-28 17:45 ` Brian Inglis [this message]
2017-01-28 19:06 ` Eric Blake
2017-01-28 19:59 ` Brian Inglis
2017-01-30 18:30 ` Jon Turney
2017-01-31 0:00 ` Steven Penny
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=a8ddccfc-6eed-0d05-b756-f95d7e5ccdf2@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).