Subject: Re: [Gnu-arch-users] Re: File naming conventions
From: Zenaan Harkness <zen@cashpoolcomps.com>
To: GNU Arch Users <gnu-arch-users@gnu.org>
In-Reply-To: <20041021020831.2c84cc20@comet>
References: <1098074588.29545.40.camel@whiskas.cashpoolcomps.com>
	<1098092294.5219.8.camel@johannes>
	<C671551A-212F-11D9-A63A-000393CFE6B8@spy.net>
	<20041018181822.GD9196@puritan.pcp.ath.cx>
	<8D7869BC-213A-11D9-A63A-000393CFE6B8@spy.net>
	<1098141434.19575.42.camel@whiskas.cashpoolcomps.com>
	<20041018233511.GA31642@fencepost>
	<1098156854.19575.65.camel@whiskas.cashpoolcomps.com>
	<buok6tn1foz.fsf@mctpc71.ucom.lsi.nec.co.jp>
	<1098163496.19575.134.camel@whiskas.cashpoolcomps.com>
	<20041019060152.GC18852@wisq.net>
	<1098311382.11967.35.camel@nemesis.xlii.org>
	<1098313564.5336.29.camel@whiskas.cashpoolcomps.com>
	<4176F429.3070209@johnmeinel.com>  <20041021020831.2c84cc20@comet>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1098319773.5336.50.camel@whiskas.cashpoolcomps.com>
Mime-Version: 1.0
Date: Thu, 21 Oct 2004 10:49:33 +1000
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 1555
Lines: 54
On Thu, 2004-10-21 at 10:08, chth@gmx.net wrote:
> > There is the command tla escape (and tla escape --unescaped). But they
> > 
> > only read a single command line argument. So you can't do:
> > 
> > tla inventory --source | tla escape --unescaped | xargs chmod 644
> > and you can't do
> > tla inventory --source | xargs tla escape --unescaped | xargs chmod
> > 644
> 
> Try:
> 
> tla inventory --source |\
>   while read line; do
>     chmod 644 "$(tla escape --unescaped "$line")";
>   done
> 
> the stream-mode was not added to tla escape because it wont handle
> newlines in filenames and wont work with leading/trailing whitespaces.
> 
> tla inventory --source --unescaped |\
>   while read line; do
>     chmod 644 "$line";
>   done
> 
> will work if you are sure that there are no newlines in filenames.

The point is, you're now basically at the bash script level.
This is not something I would feel comfortable typing in at
the command line at random points in the future.

If it works, that's certainly useful though... in which case,
I'd suggest we're back to the following:

  tla chmod
  tla ln
  ...

since the alternative is things like tla[-]chmod, which every
man and his dog will write, and you start to go "why isn't this
default". And the default convention for tla proper is a Unixy
sub-command space.

cheers
zen


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/