Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh tips for "UNIX Power Tools"
- X-seq: zsh-users 2943
- From: Bruce Stephens <bruce+zsh@xxxxxxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxxxxxx
- Subject: Re: zsh tips for "UNIX Power Tools"
- Date: 04 Mar 2000 12:31:28 +0000
- In-reply-to: "Bart Schaefer"'s message of "Sat, 4 Mar 2000 05:40:13 +0000"
- Mailing-list: contact zsh-users-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <28174.952013581@xxxxxxxxx> <20000303123932.A11036@xxxxxxxxxxxxxxxxx> <87k8jjwt6h.fsf@xxxxxxxxxxxxxxxxxxxx> <1000304054014.ZM21187@xxxxxxxxxxxxxxxxxxxxxxx>
- Sender: bruce@xxxxxxxxxxxxxxxxxxxx
"Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx> writes:
[...]
> On Mar 3, 11:05pm, Bruce Stephens wrote:
> } Subject: Re: zsh tips for "UNIX Power Tools"
> }
> } > chmod 755 **/*(/)
> } > chmod 644 **/*(.)
> }
> } What's wrong with
> }
> } chmod -R go+rX .
>
> It changes the group and other execute permissions of plain files if the
> user execute permission was already set. That's obviously not what 644
> accomplishes on plain files in Thomas's example.
Sure, the two aren't identical. I suspect the latter is more often
what people want---it's usually what I want, anyway.
> Besides, not everyone has GNU chmod.
I think the behaviour is reasonably common. Solaris 2.5.1 chmod also
works (although I don't see the +X behaviour in the manpage).
Messages sorted by:
Reverse Date,
Date,
Thread,
Author