From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Windows 10, TeXLive 2016, and grep
Date: Sat, 20 Aug 2016 12:56:42 +0200 [thread overview]
Message-ID: <68538349-4056-95bc-b70f-9ad0315171f9@wxs.nl> (raw)
In-Reply-To: <fd0de6a8-3791-8c6d-bd84-2fd2ec8ccb39@gmail.com>
On 8/20/2016 3:08 AM, Br. Samuel Springuel wrote:
> I'm looking particularly for the `-m #` (return only first # matches)
> and `-o` (return only the portion of the line which matches), with the
> latter being more important than the former.
>
> I have a line in a Unix script (where I can expect standard grep to be
> available) which looks like this:
>
> grep -m 1 'GREGORIO_VERSION' $loc | grep -o
> '[0-9]*\.[0-9]*\.[0-9]*-*[betarc]*[0-9]*' >> $OUTPUT 2>&1
>
> Basically the script is supposed to identify which version of a file in
> our package is a person has. To do this it looks for the first line in
> a file ($loc) which is marked as containing the version number (by
> looking for the text of the comment which we use to mark those lines for
> scripting purposes) and then extract the version number from that line
> (by looking for the pattern which the version number follows).
>
> In Windows, I can do the first part of this command with `findstr` (a
> native command which has similar, but not identical, functionality to
> grep, but cannot do the second at all. My current work around is to use
> the characters which precede and follow the version number to trim the
> string, but this requires me to have repetitive code because not all the
> files in our package use the same delimiting characters. What I
> accomplish in one `for` loop in the Unix version (looping over a list of
> the files in our package), I need three loops to do in Windows (breaking
> the list up by the delimiting characters). Having `mtxrun -script grep`
> support the `-o` option would enable me to consolidate and simplify the
> code.
I'll add -n=1 (--first) and --match
>rgrep --pattern="modules.-%['(.-)'%]" char-*.lua --first --match
which returns (on my machine)
char-act
char-cjk
char-def
char-enc
char-ent
char-fio
char-ini
char-map
char-rep
char-tex
char-utf
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-08-20 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 19:52 Br. Samuel Springuel
2016-08-17 8:40 ` Hans Hagen
2016-08-20 1:08 ` Br. Samuel Springuel
2016-08-20 10:56 ` Hans Hagen [this message]
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=68538349-4056-95bc-b70f-9ad0315171f9@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).