Re: BUG: locals remove setopt autonamedirs

[Oliver Kiddle <opk@xxxxxxx>]

On 7 Apr, Bart Schaefer wrote:
> However, I'm in favor of including noautonamedirs in the completion
> options, I was surprised to realize it was not there already.

The completion options were intentionally kept very much minimal in
the first place because the completion system needs to honour the
user's option choices in many areas. Note that there's no equivalent to
_comp_caller_options in the C code. Options should not be added to it
on a whim without fairly thorough consideration for whether this will
affect anything. One or two that are already there are questionable, an
example being NO_cshjunkiequotes which only doesn't matter because the
underlying C code doesn't correctly correctly handle that when quoting
matches.

In the case of autonamedirs, I've not been able to identify any problem.
So to be clear, I am not raising an objection here.

The nameddirs association is used for named directories and a variable
only becomes a named directory once it is referenced as such, e.g with
  : ~nm
Arguably completion after a tilde should offer you any variable that
contains a valid path value but I think that would be more annoying than
useful.

I'm puzzled as to why I switched to using autonamedirs instead of hash
-d long ago. I had a vague notion that something (rehash?) would cause
them to get lost again but checking zsh 3.0.3 now, that doesn't appear
to be the case. Perhaps it was even older or I'm getting muddled with
tcsh; maybe you remember.

Oliver