zsh-users
 help / color / mirror / code / Atom feed
From: Bruce Stephens <bruce+zsh@cenderis.demon.co.uk>
To: zsh-users@sunsite.auc.dk
Subject: Re: zsh tips for "UNIX Power Tools"
Date: 04 Mar 2000 12:31:28 +0000	[thread overview]
Message-ID: <87zose7w7z.fsf@cenderis.demon.co.uk> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Sat, 4 Mar 2000 05:40:13 +0000"

"Bart Schaefer" <schaefer@candle.brasslantern.com> 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).


  parent reply	other threads:[~2000-03-04 12:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-02 16:13 Jerry Peek
2000-03-03 11:39 ` Thomas Köhler
2000-03-03 14:17   ` Jerry Peek
2000-03-03 23:05   ` Bruce Stephens
2000-03-04  5:40     ` Bart Schaefer
2000-03-04 12:05       ` Thomas Köhler
2000-03-04 16:38         ` Bart Schaefer
2000-03-04 17:18           ` Bart Schaefer
2000-03-04 12:31       ` Bruce Stephens [this message]
2000-03-04 11:43     ` Thomas Köhler
2000-03-04 12:43       ` Bruce Stephens
2000-03-04 12:22     ` Vincent Lefevre
2000-03-04 18:12       ` Bart Schaefer
2000-03-05 23:19         ` Vincent Lefevre
2000-03-06  0:30           ` Bart Schaefer
2000-03-06 20:51           ` Thomas Köhler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zose7w7z.fsf@cenderis.demon.co.uk \
    --to=bruce+zsh@cenderis.demon.co.uk \
    --cc=zsh-users@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).