On Tue Dec 29 19:58:45 EST 2009, yard-...@telus.net wrote:
> erik quanstrom wrote:
>
> >
> > ; flag v && echo true
> > flag v && echo true
> > ; ed .rcrc
> > ed .rcrc
> > 900
> > 1
> > 1
> > if (test -e /etc/rcrc)
> > q
> > q
> >
>
> It looks like you're you're using the Rakitzis rc; is readline
erik quanstrom wrote:
>
> ; flag v && echo true
> flag v && echo true
> ; ed .rcrc
> ed .rcrc
> 900
> 1
> 1
> if (test -e /etc/rcrc)
> q
> q
>
It looks like you're you're using the Rakitzis rc; is readline involved?
i'm getting spurious echo in 9term on average about 2/3 of
the time. this example sees the spurious echo every time.
programs like bash that eat cooked input don't seem to suffer
the same fate.
; flag v && echo true
flag v && echo true
; ed .rcrc
ed .rcrc
900
1
1
if (test -e /etc/rcrc)
q
q
has a
The 'g' is unnecessary.
-rob
On Wed, Dec 30, 2009 at 4:59 AM, Tim Newsham wrote:
>> It is suggested to use
>> du -a | awk '{print $2}'
>> instead of find. But what if filename contains spaces? For example if
>> file is named "foo bar" then awk will output "foo" only.
>
> What about
>
> du -a
Chicken dinner!
On Tue, Dec 29, 2009 at 10:59 AM, Tim Newsham wrote:
> It is suggested to use
>> du -a | awk '{print $2}'
>> instead of find. But what if filename contains spaces? For example if
>> file is named "foo bar" then awk will output "foo" only.
>>
>
> What about
>
> du -a | sed 's/
It is suggested to use
du -a | awk '{print $2}'
instead of find. But what if filename contains spaces? For example if
file is named "foo bar" then awk will output "foo" only.
What about
du -a | sed 's/^[0-9]*//g'
no loss on spaces in filenames.
no loss on tabs in filenames.
Tim Newsham
