zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: jimkirk@uwyo.edu (James Kirkpatrick)
Cc: zefram@fysh.org, zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: chown and chgrp in files module
Date: Thu, 9 Dec 1999 17:41:23 +0000 (GMT)	[thread overview]
Message-ID: <E11w7ZD-0005l7-00@crucigera.fysh.org> (raw)
In-Reply-To: <Pine.GSO.4.10.9912091016150.10671-100000@asuwlink.uwyo.edu> from James Kirkpatrick at "Dec 9, 1999 10:20:53 am"

James Kirkpatrick wrote:
>I'm not sure I understand.  chown and chgrp are now builtins?

If you load the files module.  If you do nothing, you get the usual
external programs.  rm, mv, ln, mkdir, rmdir and sync are already
available as builtins in exactly the same way.

>                                                                  Are they
>POSIX compliant?

Almost.  chown accepts "." to separate username and group, in addition to
the POSIX ":".  This is the same level of POSIX conformance as GNU chown.

>This does not seem to be the sort of thing that should be built in to a
>shell, any more than rm, ls, find, or a C compiler :-)

It's very useful to have these things built into a statically-linked
system administration shell.  (That's where the request for a builtin
chown originated.)  In addition to the utilities I listed above, we have
a `stat' module that effectively makes possible a full implementation
of ls as a shell function, and zsh globbing with glob qualifiers very
nearly makes find redundant.

-zefram


  reply	other threads:[~1999-12-09 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09 16:02 zefram
1999-12-09 17:20 ` James Kirkpatrick
1999-12-09 17:41   ` Zefram [this message]
1999-12-09 18:19     ` James Kirkpatrick
1999-12-09 23:40     ` James Antill
1999-12-13 12:10       ` Zefram
1999-12-10 21:43     ` Clint Adams

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=E11w7ZD-0005l7-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=jimkirk@uwyo.edu \
    --cc=zsh-workers@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).