Re: "compinit -i" not excluding some insecure dirs?

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Sep 28,  5:52pm, Andrew Janke wrote:
}
} But in this case I think it *is* scanning the insecure directory: I had 
} a _foo only in /insecure, not in /secure, and it still got picked up by 
} compinit and used for completion.

Hmm.

compaudit returns true when no insecure directories are found or when
it is passed the -u option.

compinit sets _comp_secure only when compaudit returns true.

compdump writes the files from the fpath directories into the dumpfile
only when _comp_secure is set.  However, I'm not sure this accomplishes
what was intended.

And in any case compinit doesn't otherwise change its behavior when
passed -i, so yes, that's clearly a bug in the case where the dump
file does not already exist.