On 11/25/06, David Bitseff <[EMAIL PROTECTED]> wrote: > Hi, > > I set --perl-regexp in GREP_OPTIONS, and this conflicts with the options used > in contains.fish. I'm using fish 1.22.1. The --perl-regexp option is used > in GNU grep.
Nice catch - thanks for the patch. > > I'm new to fish, so my patch may not be optimal. I tried scoping the > GREP_OPTIONS variable locally to the contains function, but that didn't > appear to work. It also appears necessary to set the value to an empty > string. That is a scoping bug. It sees that if you create a local non-exported variable and a global exported variable, then the global value will be exported even though is should be shadowed by the local one. You can use set -lx GREP_OPTIONS and it works, though. At least for me. I'll see if I can't fix the bug - if so, simply using 'set -l GREP_OPTIONS' should work. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Fish-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fish-users > -- Axel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
