Fwd: Re: stability of column-widths in output from df, route etc

[David Collier]

In article <4CF05BDC.3090408 at triad.rr.com>, doug.clapp at triad.rr.com (Doug
Clapp) wrote:

> *From:* Doug Clapp <doug.clapp at triad.rr.com>
> *To:* busybox <busybox at busybox.net>
> *Date:* Fri, 26 Nov 2010 20:16:12 -0500
> 
> I'm a fan of awk.  Seems to me one awk would do what sed... | cut 
> or tr ...| cut would do - i.e. separate fields on one or more 
> consecutive space characters and allow you to pick the field(s) you 
> want.

I need to learn awk - I don't think it was in my previous build of
busybox, but I'm putting it in right now.

D




> 
> Doug
> 
> -------- Original Message --------
> Subject: 	Re: stability of column-widths in output from df, route 
> etc
> Date: 	Fri, 26 Nov 2010 15:32:42 +0100
> From: 	walter harms <wharms at bfs.de>
> Reply-To: 	wharms at bfs.de
> To: 	Joakim Tjernlund <joakim.tjernlund at transmode.se>
> CC: 	busybox at busybox.net
> 
> 
> 
> Am 26.11.2010 13:06, schrieb Joakim Tjernlund:
> >>
> >>  On Fri, Nov 26, 2010 at 11:00 AM, David Collier
> >>  <from_busybox_maillist at dexdyne.com>  wrote:
> >>>  I have some scripts which manipulate the output of route, and 
> df, by
> >>>  using cut -c8-12 or similar to extract the info I want.
> >>>
> >>>  How risky is this - what are the chances of someone making a 
> column wider
> >>>  or narrower in a future issue of busybox?
> >>>
> >>>  Is there a better technique?
> >>
> >>  Trim all whitespace to single spaces (sed 's/  */ /g'),
> >>  then separate fields on the space char.
> >
> >  Yes, although it should probably be sed 's/ \+/ /g'
> >
> 
> just because i am fan of "tr"
> tr -s " "
> 
> re,
>   wh
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
> 
> 
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
>