[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: |& in bash?
From: |
Bob Proulx |
Subject: |
Re: |& in bash? |
Date: |
Tue, 22 Jan 2013 14:36:38 -0700 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Greg Wooledge wrote:
> It kinda reminds me of the Linux newcomers who don't know how to do
> gzip -dc foo.tar.gz | tar xvf - (and so on) because they've been trained
> to use GNU tar's "z" flag instead, and therefore that piece of their
> education hasn't been absorbed yet.
Just like:
grep -r PATTERN
Has replaced:
find . -type f -exec grep PATTERN {} +
And therefore they don't know how to write other directory traversal
tasks either.
find . -type f -exec sed -n '/PATTERN/s/THIS/THAT/gp' {} +
Bob
- Re: |& in bash?, (continued)
- Message not available
- Re: |& in bash?, John Caruso, 2013/01/21
- Re: |& in bash?, Steven W. Orr, 2013/01/22
- Re: |& in bash?, Greg Wooledge, 2013/01/22
- Re: |& in bash?, Bob Proulx, 2013/01/22
- Re: |& in bash?, Andreas Schwab, 2013/01/22
- Re: |& in bash?, DJ Mills, 2013/01/22
- Re: |& in bash?, Andreas Schwab, 2013/01/23
- Re: |& in bash?, Greg Wooledge, 2013/01/22
- Re: |& in bash?,
Bob Proulx <=
- Re: |& in bash?, Linda Walsh, 2013/01/26