filename autocompletion/autocorrection misfeature

filename autocompletion/autocorrection misfeature

[Fourhundred Thecat]

Hello,

when I type beginning of a filename, and autocomplete with tab:

$ ls gs<tab>

if there is no match starting with "gs", I might get:

$ ls logs

Far from being useful, I find this feature actually harmful. I want to
know that there is no match in current dir (perhaps I entered the wrong
dir mistakenly).

To add insult to injury, the autocompleted/autocorrected filename does
not exist either (there is a file "bootlogs", but no file "logs")

How can I disable this "feature" ?
I tried adding following options into my .zshrc, but that did not help:

  DISABLE_CORRECTION="true"
  unsetopt correct
  unsetopt correct_all

thanks,

Re: filename autocompletion/autocorrection misfeature

[Daniel Shahaf]

Fourhundred Thecat wrote on Sat, Oct 08, 2016 at 08:48:18 +0200:
> $ ls gs<tab>
> $ ls logs
> 
> How can I disable this "feature" ?

It's not enabled by default; something in your setup opts in to it.
Judging by your reference to DISABLE_CORRECTION, which is not a zsh
thing at all (not in zshparams(1)), I suspect it's enabled by some
configuration framework you use.

So, you should really follow up with that framework's support venue.
However, we may be able to steer you in the right direction.  What's the
output of
.
    bindkey $'\t'
    zstyle -L \* completer
.
?

> I tried adding following options into my .zshrc, but that did not help:
> 
>   DISABLE_CORRECTION="true"
>   unsetopt correct
>   unsetopt correct_all
> 

Not sure about the first one (as I said: it's not a zsh feature), but
the latter two should be placed at the end of .zshrc to be effective.

Re: filename autocompletion/autocorrection misfeature

[Fourhundred Thecat]

> On 2016-10-08 09:40, Daniel Shahaf wrote:
>
> So, you should really follow up with that framework's support venue.
> 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

I have now disabled zsh-syntax-highlighting, and I am not using any
other framework (no oh my zsh). But the problem persists.

>> I tried adding following options into my .zshrc, but that did not help:
>>
>>   DISABLE_CORRECTION="true"
>>   unsetopt correct
>>   unsetopt correct_all
>>
> 
> Not sure about the first one (as I said: it's not a zsh feature), but
> the latter two should be placed at the end of .zshrc to be effective.

yeah, DISABLE_CORRECTION did not look like valid zsh option, but I tried
it anyway, because several people were recommending it when I googled
around.

I should also add, that I am using zsh 4.3.17

thanks for help,

Re: filename autocompletion/autocorrection misfeature

[Oliver Kiddle]

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

Re: filename autocompletion/autocorrection misfeature

[Eric Cook]

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

Re: filename autocompletion/autocorrection misfeature

[Oliver Kiddle]

Eric Cook wrote:
> > The next thing I would check is for matching control:
> >   zstyle -L \* matcher-list
>
> It appears the question was asked in multiple places.
> unix.stackexchange.com/questions/315714/disable-substring-filename-completion-in-zsh

So it is matcher-list and l:|=* in particular.

Oliver

Re: filename autocompletion/autocorrection misfeature

[Fourhundred Thecat]

> On 2016-10-13 16:22, Oliver Kiddle wrote:
>
> Eric Cook wrote:
>>> The next thing I would check is for matching control:
>>>   zstyle -L \* matcher-list
>>
>> It appears the question was asked in multiple places.
>> unix.stackexchange.com/questions/315714/disable-substring-filename-completion-in-zsh
> 
> So it is matcher-list and l:|=* in particular.
> 
> Oliver
> 

yes, the problem is solved by using:

  zstyle ':completion:*' matcher-list ''

I asked the same question on Unix Stackexchange, after I did not receive
any response here for couple of days.

Thanks,