Re: zle messes up 'words' variable?

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On May 2,  9:11pm, Felipe Contreras wrote:
}
} On Fri, Apr 29, 2011 at 6:31 AM, Bart Schaefer
} <schaefer@xxxxxxxxxxxxxxxx> wrote:
} > Your example in workers/29086 explicitly loads and runs bashcompinit.
} > What am I missing?
} 
} What is 'workers/29086'?

Sorry, I'm writing in zsh-workers subscriber-speke.  Every message sent
to the zsh-workers (or zsh-users) list is tagged with an "X-Seq:" header
containing a number.  The archive server at zsh.org is able to look up
messages by sequence number.  So we shorthand "go to the zsh.org archive
and put 29086 into the workers lookup field" as "workers/29086".
 
} I am using bashcompinit, but the issue appears without it.

Without bashcompinit, there is by definition not an issue.  Or, if you
prefer, you should have expected this issue to appear, because words is
documented as a special variable in completion function context.

If what you want to discuss is ways to fix bashcompinit so that the
functions in bash completion work as expected, that's one thing.  If
what you're asking is for the special-ness of "words" to be undone
for completion in general, that's so unlikely to happen as to not be
worth continuing.