Acme-CPANModules-GrepVariants
view release on metacpan or search on metacpan
},
{
"class" : "Dist::Zilla::Plugin::ShareDir",
"name" : "@Author::PERLANCAR/@Filter/ShareDir",
"version" : "6.033"
},
{
"class" : "Dist::Zilla::Plugin::MakeMaker",
"config" : {
"Dist::Zilla::Role::TestRunner" : {
"default_jobs" : 1
}
},
"name" : "@Author::PERLANCAR/@Filter/MakeMaker",
"version" : "6.033"
},
{
"class" : "Dist::Zilla::Plugin::Manifest",
"name" : "@Author::PERLANCAR/@Filter/Manifest",
"version" : "6.033"
},
name: '@Author::PERLANCAR/@Filter/ExecDir'
version: '6.033'
-
class: Dist::Zilla::Plugin::ShareDir
name: '@Author::PERLANCAR/@Filter/ShareDir'
version: '6.033'
-
class: Dist::Zilla::Plugin::MakeMaker
config:
Dist::Zilla::Role::TestRunner:
default_jobs: 1
name: '@Author::PERLANCAR/@Filter/MakeMaker'
version: '6.033'
-
class: Dist::Zilla::Plugin::Manifest
name: '@Author::PERLANCAR/@Filter/Manifest'
version: '6.033'
-
class: Dist::Zilla::Plugin::ConfirmRelease
name: '@Author::PERLANCAR/@Filter/ConfirmRelease'
version: '6.033'
few practical uses; mainly educational. The portability advantage of
Perl is probably minor as grep and many Unix utilities are now available
on other platforms including Windows.
2a. Improvements in recursive searching against files
ack. Created in 2005 by Andy Lester, ack is the granddaddy of grep-like
programs that try to improve the experience of using grep to search for
text in source code. ack skips VCS directories like ".git" or ".svn",
and understands file types so it doesn't look into giant ".mp4"s and
other binaries by default. ack has spurred the development of its
improvements (mostly in speed aspect) like The Silver Searcher ("ag")
(implemented in C) or "ripgrep" (implemented in Rust). "git" also now
includes a "git-grep" utility (implemented in C). ack has a website:
<https://beyondgrep.com>. See also <https://betterthanack.com>.
gre (from App::Gre) is a "grep clone using Perl regexp's with better
file filtering, defaults, speed, and presentation". It seems to focus on
providing many options to filter files (from including/excluding by file
extension, by matching against filename, by first line, by maximum
directory depth, and so on). It also offers some alternative output
styles.
2b. Improvements in searching for multiple patterns in no particular
order
Normally with the regular grep, to search for all 'foo' and 'bar' *in no
particular order*, you either have to do something like:
('foo|bar') is no problem in grep.
Some tools have been written to make it easier to specify multiple
patterns:
abgrep (from App::abgrep) sports a "--all" option to require all
patterns to appear in a line (in no particular order). Normally, when
multiple patterns are given (via multiple "-e" or "--regexp" options),
grep will include lines that just contain at least one of the patterns.
greple (from App::Greple). By default, greple only display lines that
contain all patterns, instead of just one. greple also has a few other
tricks up its sleeve, like configuration file to define complex regexes,
matching across lines, and Japanese text support.
grep-terms (from App::GrepUtils) is a grep wrapper to convert multiple
terms into a chain of look-ahead patterns like described above. This
allows you to use the standard grep.
3. Variants: alternate ways of specifying things to search for
With wcgrep (from App::wcgrep) you can search using wildcard pattern
instead of regex, which is admittedly more limited than regex.
grep-similar-to (from App::grep::similar::text lets you specify a text
and it will only show lines from input that are similar to the provided
text.
grep-sounds-like (from App::grep::sounds::like lets you specify a word
and it will only show lines from input that have words that sound like
the provided word. You can choose from one of several phonetic
algorithms like Metaphone (the default), Soundex, etc.
4a. Variants: alternate source: repository (version control system)
content and history
For git, the abovementioned "git-grep" can search for files in the work
tree as well as commit content. For Mercurial, "hg grep" accomplishes
the same. Alternatively you can dump the history then use the standard
"grep" to go through it.
4b. Variants: alternate source: Perl source code
lib/Acme/CPANModules/GrepVariants.pm view on Meta::CPAN
probably minor as grep and many Unix utilities are now available on other
platforms including Windows.
**2a. Improvements in recursive searching against files**
<prog:ack>. Created in 2005 by Andy Lester, <pm:ack> is the granddaddy of
grep-like programs that try to improve the experience of using grep to search
for text in source code. ack skips VCS directories like `.git` or `.svn`, and
understands file types so it doesn't look into giant `.mp4`s and other binaries
by default. ack has spurred the development of its improvements (mostly in speed
aspect) like The Silver Searcher (`ag`) (implemented in C) or `ripgrep`
(implemented in Rust). `git` also now includes a `git-grep` utility (implemented
in C). ack has a website: <https://beyondgrep.com>. See also
<https://betterthanack.com>.
<prog:gre> (from <pm:App::Gre>) is a "grep clone using Perl regexp's with better
file filtering, defaults, speed, and presentation". It seems to focus on
providing many options to filter files (from including/excluding by file
extension, by matching against filename, by first line, by maximum directory
depth, and so on). It also offers some alternative output styles.
**2b. Improvements in searching for multiple patterns in no particular order**
Normally with the regular grep, to search for all 'foo' and 'bar' *in no
particular order*, you either have to do something like:
lib/Acme/CPANModules/GrepVariants.pm view on Meta::CPAN
searching for aternates from multiple patterns ('foo|bar') is no problem in
grep.
Some tools have been written to make it easier to specify multiple patterns:
<prog:abgrep> (from <pm:App::abgrep>) sports a `--all` option to require all
patterns to appear in a line (in no particular order). Normally, when multiple
patterns are given (via multiple `-e` or `--regexp` options), grep will include
lines that just contain at least one of the patterns.
<prog:greple> (from <pm:App::Greple>). By default, greple only display lines
that contain all patterns, instead of just one. greple also has a few other
tricks up its sleeve, like configuration file to define complex regexes,
matching across lines, and Japanese text support.
<prog:grep-terms> (from <pm:App::GrepUtils>) is a grep wrapper to convert
multiple terms into a chain of look-ahead patterns like described above. This
allows you to use the standard grep.
**3. Variants: alternate ways of specifying things to search for**
lib/Acme/CPANModules/GrepVariants.pm view on Meta::CPAN
With <prog:wcgrep> (from <pm:App::wcgrep>) you can search using wildcard pattern
instead of regex, which is admittedly more limited than regex.
<prog:grep-similar-to> (from <pm:App::grep::similar::text> lets you specify a
text and it will only show lines from input that are similar to the provided
text.
<prog:grep-sounds-like> (from <pm:App::grep::sounds::like> lets you specify a
word and it will only show lines from input that have words that sound like the
provided word. You can choose from one of several phonetic algorithms like
Metaphone (the default), Soundex, etc.
**4a. Variants: alternate source: repository (version control system) content and history**
For git, the abovementioned `git-grep` can search for files in the work tree as
well as commit content. For Mercurial, `hg grep` accomplishes the same.
Alternatively you can dump the history then use the standard `grep` to go
through it.
**4b. Variants: alternate source: Perl source code**
lib/Acme/CPANModules/GrepVariants.pm view on Meta::CPAN
practical uses; mainly educational. The portability advantage of Perl is
probably minor as grep and many Unix utilities are now available on other
platforms including Windows.
B<2a. Improvements in recursive searching against files>
L<ack>. Created in 2005 by Andy Lester, L<ack> is the granddaddy of
grep-like programs that try to improve the experience of using grep to search
for text in source code. ack skips VCS directories like C<.git> or C<.svn>, and
understands file types so it doesn't look into giant C<.mp4>s and other binaries
by default. ack has spurred the development of its improvements (mostly in speed
aspect) like The Silver Searcher (C<ag>) (implemented in C) or C<ripgrep>
(implemented in Rust). C<git> also now includes a C<git-grep> utility (implemented
in C). ack has a website: L<https://beyondgrep.com>. See also
L<https://betterthanack.com>.
L<gre> (from L<App::Gre>) is a "grep clone using Perl regexp's with better
file filtering, defaults, speed, and presentation". It seems to focus on
providing many options to filter files (from including/excluding by file
extension, by matching against filename, by first line, by maximum directory
depth, and so on). It also offers some alternative output styles.
B<2b. Improvements in searching for multiple patterns in no particular order>
Normally with the regular grep, to search for all 'foo' and 'bar' I<in no
particular order>, you either have to do something like:
% grep --color=always foo FILES | grep bar
lib/Acme/CPANModules/GrepVariants.pm view on Meta::CPAN
searching for aternates from multiple patterns ('foo|bar') is no problem in
grep.
Some tools have been written to make it easier to specify multiple patterns:
L<abgrep> (from L<App::abgrep>) sports a C<--all> option to require all
patterns to appear in a line (in no particular order). Normally, when multiple
patterns are given (via multiple C<-e> or C<--regexp> options), grep will include
lines that just contain at least one of the patterns.
L<greple> (from L<App::Greple>). By default, greple only display lines
that contain all patterns, instead of just one. greple also has a few other
tricks up its sleeve, like configuration file to define complex regexes,
matching across lines, and Japanese text support.
L<grep-terms> (from L<App::GrepUtils>) is a grep wrapper to convert
multiple terms into a chain of look-ahead patterns like described above. This
allows you to use the standard grep.
B<3. Variants: alternate ways of specifying things to search for>
lib/Acme/CPANModules/GrepVariants.pm view on Meta::CPAN
With L<wcgrep> (from L<App::wcgrep>) you can search using wildcard pattern
instead of regex, which is admittedly more limited than regex.
L<grep-similar-to> (from L<App::grep::similar::text> lets you specify a
text and it will only show lines from input that are similar to the provided
text.
L<grep-sounds-like> (from L<App::grep::sounds::like> lets you specify a
word and it will only show lines from input that have words that sound like the
provided word. You can choose from one of several phonetic algorithms like
Metaphone (the default), Soundex, etc.
B<4a. Variants: alternate source: repository (version control system) content and history>
For git, the abovementioned C<git-grep> can search for files in the work tree as
well as commit content. For Mercurial, C<hg grep> accomplishes the same.
Alternatively you can dump the history then use the standard C<grep> to go
through it.
B<4b. Variants: alternate source: Perl source code>
( run in 0.452 second using v1.01-cache-2.11-cpan-0a6323c29d9 )