-- Forwarded message --
From: Agus <[EMAIL PROTECTED]>
Date: 05-jul-2007 10:09
Subject: Re: grep question
To: Paul procacci <[EMAIL PROTECTED]>
2007/7/4, Paul procacci <[EMAIL PROTECTED]>:
ann kok wrote:
> Hi all
>
> how can I use grep to have the
ann kok wrote:
> Hi all
>
> how can I use grep to have the output as 60.40.2.x
>
> eg:
> 60.40.2.5
> 60.40.2.3
> 60.40.2.7
>
> except 60.40.2x.x
>
> eg:
> 60.40.20.5
> 60.40.23.6
> 60.40.25.7
>
> Thank you
>
>
>
>
>
>
> how can I use grep to have the output as 60.40.2.x
>
> eg:
> 60.40.2.5
> 60.40.2.3
> 60.40.2.7
>
> except 60.40.2x.x
>
> eg:
> 60.40.20.5
> 60.40.23.6
> 60.40.25.7
I don't know if you WANT to have 2x, or just 2., it would of been better
if you provided what you tried. Nonetheless, I've do
ann kok wrote:
> Hi all
>
> how can I use grep to have the output as 60.40.2.x
>
> eg:
> 60.40.2.5
> 60.40.2.3
> 60.40.2.7
>
> except 60.40.2x.x
>
> eg:
> 60.40.20.5
> 60.40.23.6
> 60.40.25.7
>
> Thank you
>
>
>
>
>
>
On Wednesday 04 July 2007, ann kok wrote:
> Hi all
>
> how can I use grep to have the output as 60.40.2.x
>
> eg:
> 60.40.2.5
> 60.40.2.3
> 60.40.2.7
>
> except 60.40.2x.x
>
> eg:
> 60.40.20.5
> 60.40.23.6
> 60.40.25.7
>
> Thank you
grep '60\.40\.2\.[0-9]*'
HTH,
Pieter de Goeje
___
Hi all
how can I use grep to have the output as 60.40.2.x
eg:
60.40.2.5
60.40.2.3
60.40.2.7
except 60.40.2x.x
eg:
60.40.20.5
60.40.23.6
60.40.25.7
Thank you
Park yourself in front of a worl
On Tue, Feb 08, 2005 at 03:44:47AM +0100, Anthony Atkielski wrote:
> Giorgos Keramidas writes:
>
> GK> It may not be related to what you are seeing, but grep(1)
> GK> is locale-aware. What it considers a "text" character
> GK> depends on the current locale settings.
>
> I tried setting LC_ALL to
On 2005-02-08 03:49, Anthony Atkielski <[EMAIL PROTECTED]> wrote:
> I'm looking for the hex character 93, which is an opening double
> quotation mark in the Windows character set, not the literal string
> "\0x93". Unless I'm mistaken, \0x93 in a regular expression means
> "the character whose hex
Michael C. Shultz writes:
> I made a text file named test.log containing:
>
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> grep -R "\0x93" /www/htdocs
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> aj[[CFPWJJVCVMLKFD
> a
Giorgos Keramidas writes:
GK> It may not be related to what you are seeing, but grep(1)
GK> is locale-aware. What it considers a "text" character
GK> depends on the current locale settings.
I tried setting LC_ALL to en_US.UTF-8, en_US.ISO8859-15, and
en_US.ISO8859-1, with no effect. The charact
Anthony Atkielski wrote:
> Does anyone know why
>
> grep -R "\0x93" /www/htdocs
>
> turns up only binary files, even when I know there are text
> files in the directory that contain this character? Is
> there something special about the way I specify the search
> string that causes grep to behav
On Monday 07 February 2005 05:56 pm, Anthony Atkielski wrote:
> Does anyone know why
>
> grep -R "\0x93" /www/htdocs
>
> turns up only binary files, even when I know there are text files in
> the directory that contain this character? Is there something
> special about the way I specify the search
Does anyone know why
grep -R "\0x93" /www/htdocs
turns up only binary files, even when I know there are text files in the
directory that contain this character? Is there something special about
the way I specify the search string that causes grep to behave
differently? When I specify an 8-bit c
13 matches
Mail list logo