From: "Benjamin R. Haskell" <zsh@benizi.com>
To: Lewis Thompson <purple@lewiz.net>
Cc: zsh-users@zsh.org
Subject: Re: zsh doesn't complete for tar, zip, possibly other files
Date: Tue, 15 Mar 2011 14:40:02 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1103151420350.2792@hp> (raw)
In-Reply-To: <AANLkTi=uth8SAmJC5yxUkzBYHAB-aMyPbpYhBUVPGiky@mail.gmail.com>
On Tue, 15 Mar 2011, Lewis Thompson wrote:
> partlow ~ % tar xvf [hammering TAB]
>
> So clearly completion is trying to do something. Other useful info:
If you type <ctrl+x><h> at the point where you're hammering TAB, you'll
get some debugging information that could be useful.
> I believe these are all of my completion settings in .zshrc:
>
> [...]
> zstyle ':completion:*' matcher-list '' 'l:|=* r:|=*' 'r:|[._-]=**
> r:|=**' 'm:{[:lower:][:up
> per:]}={[:upper:][:lower:]}'
I assume this was mangled by mailing (extra newlines)? But, even that line when
demangled, along with this other line you listed:
> zstyle ':completion:*' file-sort access
causes the problems you describe. I have no idea what that matcher-list
is trying to do, but this is a full, reproducible test-case for me:
==> badzshrc <==
zstyle ':completion:*' file-sort access
zstyle ':completion:*' matcher-list '' 'l:|=* r:|=*' 'r:|[._-]=** r:|=**' 'm:{[:lower:][:upper:]}={[:upper:][:lower:]}'
autoload -Uz compinit
compinit
================
$ zsh -f
$ . ./badzshrc
$ tar xvf [Tab]
At that point, ^xh produces:
tags in context :completion::complete:tar::
globbed-files (_files _tar_archive _tar (eval))
Whereas the working case produces:
tags in context :completion::complete:tar::
globbed-files (_files _tar_archive _tar (eval))
directories (_files _tar_archive _tar (eval))
all-files (_files _tar_archive _tar (eval))
--
Best,
Ben
next prev parent reply other threads:[~2011-03-15 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 18:03 Lewis Thompson
2011-03-15 18:40 ` Benjamin R. Haskell [this message]
2011-03-16 9:42 ` Lewis Thompson
2011-03-16 14:43 ` Bart Schaefer
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=alpine.LNX.2.01.1103151420350.2792@hp \
--to=zsh@benizi.com \
--cc=purple@lewiz.net \
--cc=zsh-users@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).