I have just noticed that regex seems to be broken in my Fedora 20 (just updated to latest).
Any regex search in vi, gawk, grep -E etc fails.
Any ideas?
Cheers, Stephen Davies
On 09/07/14 13:47, Joe Zeff wrote:
On 07/08/2014 08:47 PM, Stephen Davies wrote:
Any ideas?
Any details?
For example,
/^xx
or
:g/^xx/s/xx/yy/
in vi finds nothing in a file with many lines starting with xx.
Similarly grep -E "^xx" and gawk '/^xx/{print}'.
In all cases, omitting the ^ finds the relevant lines (plus a whole lot more).
Difference: one with and one without regex.
HTH, Stephen
On 07/09/14 12:21, Stephen Davies wrote:
On 09/07/14 13:47, Joe Zeff wrote:
On 07/08/2014 08:47 PM, Stephen Davies wrote:
Any ideas?
Any details?
For example,
/^xx
or
:g/^xx/s/xx/yy/
in vi finds nothing in a file with many lines starting with xx.
Similarly grep -E "^xx" and gawk '/^xx/{print}'.
In all cases, omitting the ^ finds the relevant lines (plus a whole lot more).
Difference: one with and one without regex.
[egreshko@meimei ~]$ cat stuff This is a file with xx stuff in it. This doesn't start with xx xx but this does x and this does not
[egreshko@meimei ~]$ grep -E "^xx" stuff xx but this does
Fully updated this AM.
Mea culpa :-(
Twice over in fact.
1. I hadn't noticed that the files in question were all DOS files sent to me by a windows user ( so trailing $ searches failed) and
2. I hadn't noticed that all lines started with a space.
Elderly blindness. Sorry.
Cheers, Stephen
On 09/07/14 14:08, Ed Greshko wrote:
On 07/09/14 12:21, Stephen Davies wrote:
On 09/07/14 13:47, Joe Zeff wrote:
On 07/08/2014 08:47 PM, Stephen Davies wrote:
Any ideas?
Any details?
For example,
/^xx
or
:g/^xx/s/xx/yy/
in vi finds nothing in a file with many lines starting with xx.
Similarly grep -E "^xx" and gawk '/^xx/{print}'.
In all cases, omitting the ^ finds the relevant lines (plus a whole lot more).
Difference: one with and one without regex.
[egreshko@meimei ~]$ cat stuff This is a file with xx stuff in it. This doesn't start with xx xx but this does x and this does not
[egreshko@meimei ~]$ grep -E "^xx" stuff xx but this does
Fully updated this AM.
On Wed, Jul 09, 2014 at 02:16:21PM +0930, Stephen Davies wrote:
Mea culpa :-(
Twice over in fact.
- I hadn't noticed that the files in question were all DOS files sent to me
by a windows user ( so trailing $ searches failed) and
- I hadn't noticed that all lines started with a space.
Elderly blindness. Sorry.
A weakly related note about regexes; if your regex uses ranges, or character classes, your results may vary depending on your current locale!
On 09.07.2014, Stephen Davies wrote:
- I hadn't noticed that all lines started with a space.
Way back in 19-something (guess it was 1993) when I poked around with Powerbasic, I remember there was a function called trim(), which removed the whitespace on both ends of a string :-)
-
Ed Greshko -
Heinz Diehl -
Joe Zeff -
Stephen Davies -
Suvayu Ali