From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Adam Spiers <adam@spiers.net>,
zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: _find or _users broken?
Date: Sat, 29 Apr 2000 17:39:06 +0000 [thread overview]
Message-ID: <1000429173906.ZM32406@candle.brasslantern.com> (raw)
In-Reply-To: <20000429135806.A2543@thelonious.new.ox.ac.uk>
On Apr 29, 1:58pm, Adam Spiers wrote:
} Subject: _find or _users broken?
}
} $ find -user <TAB>
} ---- user
} ---- directory
} <list of directories and users together>
} $ find ! -user <TAB>
} ---- directory
} <list of directories>
}
} Why is it completing directories at all? And when it completes users
} and directories, why are the users listed under the directory group?
That part must have something to do with your settings. The final clause
of the _arguments call in _find is to complete directories when nothing
else matches.
There is something going wrong, though:
zagzig[103] find -user <TAB>
Completing user
(list of users only)
zagzig[103] find /tmp -user <TAB>
(feep, no completions)
This (and your case with `!') appears to happen because comparguments
believes the list of options to have been finished when /tmp was put
on the line, i.e., it doesn't deal well with commands whose options
follow a list of non-option arguments.
It may be necessary to rewrite _find using _regex_arguments, or to go
to a state-machine rather than a simple usage of _arguments. I'm not
yet clever enough with _arguments to figure out a workaround, and I'm
totally unfamiliar with _regex_arguments.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~2000-04-29 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-29 12:58 Adam Spiers
2000-04-29 17:39 ` Bart Schaefer [this message]
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=1000429173906.ZM32406@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=adam@spiers.net \
--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).