Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: Grep for tab character
References:	<opsmhbyxl1ov81ve AT mail DOT optusnet DOT com DOT au> <20050220051340 DOT GA30669 AT trixie DOT casa DOT cgf DOT cx>
Message-ID:	<opsmhebkrbov81ve@mail.optusnet.com.au>
From:	Robert Mark Bram <relaxedrob AT optusnet DOT com DOT au>
MIME-Version:	1.0
Date:	Sun, 20 Feb 2005 16:46:22 +1100
In-Reply-To:	<20050220051340.GA30669@trixie.casa.cgf.cx>
User-Agent:	Opera7.23/Win32 M2 build 3227
X-IsSubscribed:	yes

Hi Christopher,

Thank you for your response!

> How about just using the actual tab character?  I don't see any 
> indication that
> grep is supposed to treat '\t' specially and it seems to behave that way 
> on linux,
> too.

I have read in many places that \t is a metacharacter for tab in regular 
expressions - but maybe that's only for sed, perl, awk etc...
http://sitescooper.org/tao_regexps.html


> What's wrong with just using tab?

Because that starts up auto-complete. In other words, I don't know how to 
insert a literal tab into a command line.

But I do not like that idea for scripts either - it can be difficult to 
visually discriminate a tab from a space character, which can too easily 
lead to errors.

Rob
:)


-- 
Robert Mark Bram
http://phd.netcomp.monash.edu.au/RobertMarkBram/default.asp
B.Comp.(Systems Development/Business Systems)
B.Net.Comp.(Hons)
Doctor of Philosophy Student

School of Network Computing
Faculty of Information Technology
Monash University
Peninsula Campus
McMahons Rd
Frankston, VIC 3199
AUSTRALIA


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -