non-executables in PATH and tab-completion

non-executables in PATH and tab-completion

[Dominik Vogt]

If there are files without executable flags in the PATH, zsh still
completes these.  (a)  Is this a bug?  (b) can this be disabled?

Example:

 $ mkdir -p ~/tmp/bin
 $ cd ~/tmp/bin
 $ touch foo.sh foo.bar
 $ chmod 640 foo.bar
 $ chmod 750 foo.sh
 $ export PATH="$HOME/tmp/bin:$PATH"
 $ hash -rf
 $ foo.<tab>
 foo.bar  foo.sh

Tab is bound to "expand-or-complete".

 $ zsh --version
 zsh 5.7.1 (x86_64-debian-linux-gnu)

Ciao

Dominik ^_^  ^_^

--

Dominik Vogt

Re: non-executables in PATH and tab-completion

[Peter Stephenson]

> On 08 March 2021 at 16:10 Dominik Vogt <dominik.vogt@gmx.de> wrote: 
> If there are files without executable flags in the PATH, zsh still
> completes these.  (a)  Is this a bug?  (b) can this be disabled?

This option is what you need to know about...  it's not specific to
completion, which just uses the normal command hash table.

HASH_EXECUTABLES_ONLY
       When  hashing  commands  because  of  HASH_CMDS,  check that the file to be
       hashed is actually an executable.  This option is unset by  default  as  if
       the  path  contains  a large number of commands, or consists of many remote
       files, the additional tests can take a  long  time.   Trial  and  error  is
       needed to show if this option is beneficial.

pws