zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Akinori MUSHA <knu@iDaemons.org>
Cc: zsh-workers@sunsite.dk
Subject: Re: _chflags
Date: Thu, 02 Aug 2001 13:21:01 +0100	[thread overview]
Message-ID: <3B6945AD.AFDEA069@yahoo.co.uk> (raw)
In-Reply-To: <864rrrvd3m.wl@archon.local.idaemons.org>

Akinori MUSHA wrote:

> Attached is the compdef for *BSD's chflags(1) command, which changes
> special file flags.  Please add it if it's okay.

I'll add that (and the _sysctl change).

Is the nodump flag defintely turned off with nonodump then (as opposed
to just dump)?

According to the man page you referenced, the flags are specified as a
comma separated list so I would suggest you replace the flags= and
compadd lines with something like:

_values -s , 'file flag'
{no,}{arch,opaque,nodump,sappnd,schg,sunlnk,uappnd,uchg,uunlnk}

but if descriptions for the flags might be useful, you could use things
like:
'(noarch)arch[set archived]' to _values.
It would be nice to use _arguments for the options. Are the options
different on net/openbsd or different versions of FreeBSD? Do they all
use the comma separated list of flags?

Oliver

_____________________________________________________________________
This message has been checked for all known viruses by the 
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp


  reply	other threads:[~2001-08-02 13:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 18:39 _chflags Akinori MUSHA
2001-08-02 12:21 ` Oliver Kiddle [this message]
2001-08-02 13:25   ` _chflags Akinori MUSHA
2001-08-02 16:19     ` _chflags Oliver Kiddle
2001-08-02 17:40       ` _chflags Akinori MUSHA
2001-08-03 11:46         ` _chflags Oliver Kiddle
2001-08-03  8:25       ` _chflags Sven Wischnowsky
2001-08-06 11:36         ` grouping inverses and sorting in completion lists (was _chflags) Oliver Kiddle

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=3B6945AD.AFDEA069@yahoo.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=knu@iDaemons.org \
    --cc=zsh-workers@sunsite.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).