From: Eric Cook <llua@gmx.com>
To: zsh-users@zsh.org
Subject: Re: filename autocompletion/autocorrection misfeature
Date: Thu, 13 Oct 2016 09:34:51 -0400 [thread overview]
Message-ID: <aedcccdc-451a-1e4a-663d-c9c7a268afc5@gmx.com> (raw)
In-Reply-To: <9277.1476350689@hydra.kiddle.eu>
On 10/13/2016 05:24 AM, Oliver Kiddle wrote:
> On 8 Oct, Fourhundred Thecat wrote:
>>> However, we may be able to steer you in the right direction. What's the
>>> output of
>>> .
>>> bindkey $'\t'
>>> zstyle -L \* completer
>>> .
>>
>> the output is:
>>
>> "^I" expand-or-complete
>> zstyle ':completion:*' completer _expand _complete
>
> Nothing there looks like the cause though it seems strange to combine _expand
> with expand-or-complete. Normally, you would either stick with using
> expand-or-complete as the default or bind tab to complete-word and then
> carefully configure _expand to your taste.
>
> The next thing I would check is for matching control:
> zstyle -L \* matcher
> zstyle -L \* matcher-list
>
> If that doesn't work, try bisecting your entire .zshrc until you
> narrow down that line or lines that cause the problem. You can also
> run zsh -f to start with a clean setup and paste in lines.
>
> Oliver
>
It appears the question was asked in multiple places.
unix.stackexchange.com/questions/315714/disable-substring-filename-completion-in-zsh
next prev parent reply other threads:[~2016-10-13 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57F896B2.9010506__48050.8810993799$1475909404$gmane$org@gmx.ch>
2016-10-08 7:40 ` Daniel Shahaf
2016-10-08 8:04 ` Fourhundred Thecat
2016-10-13 9:24 ` Oliver Kiddle
2016-10-13 13:34 ` Eric Cook [this message]
2016-10-13 14:22 ` Oliver Kiddle
2016-10-13 17:35 ` Fourhundred Thecat
2016-10-08 6:48 Fourhundred Thecat
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=aedcccdc-451a-1e4a-663d-c9c7a268afc5@gmx.com \
--to=llua@gmx.com \
--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).