GNU bug report logs - #36960
mistake with v param

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36960 in the body.
You can then email your comments to 36960 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Daniele Grassini <danielegrassini <at> libero.it>
To: bug-grep <at> gnu.org
Subject: mistake with v param
Date: Wed, 7 Aug 2019 17:45:32 +0200

hi to all.

for first i'm very sorry for my english..

when i'm using grep in this way to get the module path:

    cd $(sudo modprobe -v --show-depends r8168 | grep -Eoi 
"(\/[[:alnum:]\.\-]+){1,}" | grep -ivE "[a-z]{1}[0-9]+\.ko$")

...it return nothing

but if i switch '-v' to '-o' to test the command, it will print the right :

    $ sudo modprobe -v --show-depends r8168 | grep -Eoi 
"(\/[[:alnum:]\.\-]+){1,}" | grep -ioE "[a-z]{1}[0-9]+\.ko$"

    $ r8168.ko

so why the '-o' option check the regular exp, but the '-v' don't do his 
job??

Many Thanks

Regards

Message #12 received at 36960-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Daniele Grassini <danielegrassini <at> libero.it>
Cc: 36960-done <at> debbugs.gnu.org
Subject: Re: bug#36960: mistake with v param
Date: Thu, 2 Jan 2020 01:46:24 -0800

On 8/7/19 8:45 AM, Daniele Grassini wrote:
> so why the '-o' option check the regular exp, but the '-v' don't do his job??

The -v option was working as documented. It means, "select lines that *don't"
match the pattern", and since all input lines matched your pattern grep didn't
output anything.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.