Re: Off topic question about grep

2010-11-09 Thread ~Stack~
On 11/09/2010 12:26 PM, Bob McGowan wrote: > On 11/09/2010 06:00 AM, Jochen Schulz wrote: ... >> What was your exact command line? Did you quote the regular expression? >> My guess is that the shell interpreted the '*' character for you and you >> ended up with a command line like this: >> >> $ gre

Re: Off topic question about grep

2010-11-09 Thread Bob McGowan
On 11/09/2010 06:00 AM, Jochen Schulz wrote: > ~Stack~: >> >> But that would match against 9_asD which begins with a number (not what >> I wanted). So I tried: >> [_a-zA-Z][_a-zA-Z0-9]* >> >> I realize that the expression won't do what I mistakenly thought I >> wanted it to do. What is puzzling to

Re: Off topic question about grep

2010-11-09 Thread Paul E Condon
On 20101109_071001, ~Stack~ wrote: > Hello everyone! > > I ran into a strange issue with grep and I was hoping someone could > explain what I feel is an oddity. > > I was trying to match a word that starts with either a _ or a letter > followed by any number of _, letters, or numbers. (eg: Good =

Re: Off topic question about grep

2010-11-09 Thread Jochen Schulz
~Stack~: > > But that would match against 9_asD which begins with a number (not what > I wanted). So I tried: > [_a-zA-Z][_a-zA-Z0-9]* > > I realize that the expression won't do what I mistakenly thought I > wanted it to do. What is puzzling to me is that my hard disk usage > peaked, my cpu jumped