GNU bug report logs - #16844
Facing some issues while creating one regular expression

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 16844 in the body.
You can then email your comments to 16844 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: Machindra Dharmadhikari <machindra89 <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: Facing some issues while creating one regular expression
Date: Sat, 22 Feb 2014 17:23:38 +0530

[Message part 1 (text/plain, inline)]

Hi Team,

Could you please help me to create one regular expression. I think this (*)
special character has not handled in egrep. because i have tried it many
ways but couldn't get required expression.

Could you please help me in this.

Problem : File contains following lines:
#* hard maxlogins 10
@Student hard maxlogins 10
* hard maxlogins 10
hard maxlogins 10
#* hard maxlogins 1024

I want to find only below line from above file. but * is not handling in
regular expression:
* hard maxlogins 10


10 can be replaced by any value. and hard can be - as well. I want to these
cases as well.

Thanks & Regards,
Machindra Dharmadhikari

[Message part 2 (text/html, inline)]

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: 16844-done <at> debbugs.gnu.org
Subject: Re:  Facing some issues while creating one regular expression
Date: Sat, 08 Mar 2014 11:24:24 -0800

The regular expression '\*' matches the string '*'.

Previous Next

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