_files with match-specs

_files with match-specs

[Eric Cook]

Hey,
Not sure if i am doing something incorrect here but:

% _foo() _files -M 'L:|+='; compdef _foo foo

then
% foo +<tab>
Complete files, but removes the leading +.

When i give the same match-spec to compadd directly, it works as i expected.

% _foo() compadd -M 'L:|+=' -- *(N); compdef _foo foo

then
% foo +<tab>

Is the behavior of _files expected? If so, how should I go about
completing filenames, ignoring a possible leading + character?

Re: _files with match-specs

[Daniel Shahaf]

Eric Cook wrote on Tue, May 05, 2015 at 23:48:38 -0400:
> Hey,
> Not sure if i am doing something incorrect here but:
> 
> % _foo() _files -M 'L:|+='; compdef _foo foo
> 
> then
> % foo +<tab>
> Complete files, but removes the leading +.
> 
> When i give the same match-spec to compadd directly, it works as i expected.
> 
> % _foo() compadd -M 'L:|+=' -- *(N); compdef _foo foo
> 
> then
> % foo +<tab>
> 
> Is the behavior of _files expected?

Don't know.

> If so, how should I go about completing filenames, ignoring a possible
> leading + character?

'_f() { compset -P +; _files }', perhaps?

Daniel

Re: _files with match-specs

[Eric Cook]

On 05/06/2015 08:48 PM, Daniel Shahaf wrote:

>> If so, how should I go about completing filenames, ignoring a possible
>> leading + character?
> 
> '_f() { compset -P +; _files }', perhaps?
> 
> Daniel
> 
Ah, I forgot about compset. That works for the use case that I had.

Thank you.

Re: _files with match-specs

[Bart Schaefer]

On May 5, 11:48pm, Eric Cook wrote:
}
} % _foo() _files -M 'L:|+='; compdef _foo foo
} 
} then
} % foo +<tab>
} Complete files, but removes the leading +.

Hm.  It's happening because _path_files passes (-p '') to compadd.  I've
not yet further investigated why the -p (hidden-prefix) option has this
interaction with -M (matcher-list), perhaps someone else has insight.