Re: bash 4.4-rc1 EXECIGNORE not fully working?

[Greg Wooledge]

On Fri, Mar 18, 2016 at 10:27:54AM -0600, Eric Blake wrote:
> What were you expecting to have happen?  EXECIGNORE only controls
> whether a file matching the glob is excluded from tab completions (which
> it sounds like it did), not whether bash will avoid executing it (and
> you proved that it is still executable).

The man page says,

       EXECIGNORE
              A colon-separated list of shell patterns (see Pattern  Matching)
              defining  the list of filenames to be ignored by command search.
              Files whose full pathnames match one of these patterns  are  not
              considered  executable  files for the purposes of completion and
              command execution.

I believe this agrees more with Dennis's interpretation.