bug#30451: I found problem not solved to my grep

2018-02-13 Thread Budi
I tried to customize grep: Code: g () { if [ -n "$2" ] then i= for s in $2 do i="$i --include=*.$s" done else i='--include=*.txt --include=*.ini --include=*.*sh --include=*.c* --include=*.h --include=*.js --include=*.reg' fi grep -P -e \'$1\' -r $i } or with double quote "

bug#30713: maybe a bug report, please check(ScanMail has removed a file)

2018-03-05 Thread Budi
if use -r need -- include= gpio_pins.c after grep -iPe ' ' On 3/6/18, Paul Eggert wrote: > On 03/05/2018 02:26 AM, maik.bre...@continental-corporation.com wrote: >> So the problem for me is that I can not find "gpioPwm5" in gpio_pins.c, >> when I perform 'grep -irn "gpioPwm5"'. > > Most likely

bug#34951: [PATCH] grep: a kwset matcher not work in a grep matcher

2019-03-22 Thread Budi
How make grep walinh through FS by scanning breadth first instead of the usual depth On 3/23/19, Norihiro Tanaka wrote: > On Sat, 23 Mar 2019 08:06:35 +0900 > Norihiro Tanaka wrote: > >> A kwset matcher is not built in a grep matcher after token re-order is >> introduced in commit 5c7a0371823876

bug#34951: [PATCH] grep: a kwset matcher not work in a grep matcher

2019-03-22 Thread Budi
How make grep walking through FS by scanning breadth first instead of On 3/23/19, Budi wrote: > How make grep walinh through FS by scanning breadth first instead of > the usual depth > > On 3/23/19, Norihiro Tanaka wrote: >> On Sat, 23 Mar 2019 08:06:35 +0900 >> Norihiro

bug#31913: A bug with grep

2018-06-20 Thread Budi Kusasi
it won't. because it's insensitive to case ie. ignoring to distinguish the difference of letter case.