From: "Bart Schaefer" <schaefer@brasslantern.com>
To: johan_sundstrom@bigfoot.com, zsh mailinglist <zsh-users@math.gatech.edu>
Subject: Re: Compctl completion tweaking
Date: Tue, 23 Jun 1998 12:38:19 -0700 [thread overview]
Message-ID: <980623123820.ZM758@candle.brasslantern.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C358FC264=2E1C7A9EFA=40bigfoot=2Ecom=3E?= =?iso-8859-1?Q?Comments=3A_In_reply_to_=22Johan_Sundstr=F6m=22_=3Cjohan_s?= =?iso-8859-1?Q?undstrom=40bigfoot=2Ecom=3E?= =?iso-8859-1?Q?________=22Compctl_completion_tweaking=22_=28Jun_23=2C__4?= =?iso-8859-1?Q?=3A57pm=29?=
On Jun 23, 4:57pm, Johan Sundström wrote:
} Subject: Compctl completion tweaking
}
} I've been trying for some time to limit completion behaviour for some
} commands in an intelligent manner. What I am trying to do is mask out
} files not matching a given pattern, keeping directories intact
In 3.1.4, what you'd want (I think) is
compctl -g '*.rpm(.)' -/ rpm
The -/ flag is new and means "filesystem paths". You may not even need
the (.) in the -g pattern, unless you have some files with .rpm extensions
that aren't plain files.
} better still, matching files according to some pattern and directories
} according to some other pattern. Shouldn't that be possible using
} something like -g '(*.rpm(.))|(*(-/))'?
Unfortunately, qualifiers can only be appended at the end of an entire
glob. If you parenthesize them in an alternation like that, they're
taken as part of the pattern rather than as qualifiers.
} Secondly, is there any way I can influence the sorting compctl does?
Not at present.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1998-06-23 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-23 14:57 Johan Sundström
1998-06-23 19:38 ` 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=980623123820.ZM758@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=johan_sundstrom@bigfoot.com \
--cc=zsh-users@math.gatech.edu \
/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).