From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Disable all-files completions in a directory
Date: Sun, 03 Mar 2013 18:30:26 -0800 [thread overview]
Message-ID: <130303183026.ZM5657@torch.brasslantern.com> (raw)
In-Reply-To: <CAHjjW14Vb2yY7ckqQk=Ck4gGpvBdJHJpJ5H8w4ivAdRzinJd=Q@mail.gmail.com>
On Mar 3, 5:47pm, joe M wrote:
} Subject: Re: Disable all-files completions in a directory
}
} > You might experiment with using the file-patterns style to break up the
} > files into groups regardless of what directory you are in.
}
} wondering if you see anything weird that might be messing with the
} file-patterns.
No, but I did just discover a bug with _next_tags. I haven't figured out
how to reproduce it, but the effect is that it's possible to get the
compprefuncs variable set to
_next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre
_next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre
_next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre
_next_tags_pre _next_tags_pre _next_tags_pre _next_tags_pre
which pretty much goes nuts skipping over all your possible tags as soon
as you start the subsequent completion. I think.
Anyway MOST of the time the zstyle you tried works for me. It's only if
I've done something to trigger repetitive compprefuncs falue that things
go off the rails. So I don't know if that's what happened to you, or if
there is some other obscure interaction with the rest of your styles.
--
Barton E. Schaefer
prev parent reply other threads:[~2013-03-04 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 18:26 joe M
2013-03-03 19:36 ` Bart Schaefer
2013-03-03 22:47 ` joe M
2013-03-04 2:30 ` 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=130303183026.ZM5657@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).