From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "E. Jay Berkenbilt" <ejb@ql.org>, zsh-users@sunsite.auc.dk
Subject: Re: 3.1.9 completion problems: automounter
Date: Tue, 12 Sep 2000 06:14:35 +0000 [thread overview]
Message-ID: <1000912061435.ZM5741@candle.brasslantern.com> (raw)
In-Reply-To: <1000912052009.ZM5715@candle.brasslantern.com>
On Sep 12, 5:20am, Bart Schaefer wrote:
}
} Hmm. I've just been playing with zsh on a machine at work that has an
} automounted directory, and I can't reproduce the behavior you described.
[...]
} with the trailing slash, the mount happens and I get completions. This
} happens both with and without the new completion system loaded.
I'm sorry, I was mistaken about having loaded new completion. With the
new completion system *properly* loaded, I *can* get this to happen.
So here's the answer to your question:
zstyle -e ':completion:*' file-patterns '[[ -d $PREFIX:h/. ]]'
This tests whether the prefix (or "/", if there's no prefix, but that's
harmless) contains a "." directory, then ignores the result; so the only
effect is to force the directory to be automounted. Since it does not
set a value for $reply (see the "zstyle -e" doc), completion proceeds as
if the style were not set at all.
Note that if you actually *want* to set file-patterns for some other
context, you'll have to add the test to those styles as well, or the
side-effect will go away in those contexts.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-09-12 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-11 14:36 E. Jay Berkenbilt
2000-09-11 17:33 ` more wishes with automounter Alexandre Duret-Lutz
2000-09-12 6:58 ` Bart Schaefer
2000-09-13 9:32 ` Alexandre Duret-Lutz
2000-09-13 15:02 ` Bart Schaefer
2000-09-12 5:20 ` 3.1.9 completion problems: automounter Bart Schaefer
2000-09-12 6:14 ` 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=1000912061435.ZM5741@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=ejb@ql.org \
--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).