Bug in completion with curly braces?

[Felipe Contreras <felipe.contreras@xxxxxxxxx>]

Hello,

While adding unquoted completions such as "stash@{0}" the completion
system gets confused while inside the curly braces.

For example, given:

  compadd -Q -- 'stash@{0}' 'stash@{1}'

The first completion correctly generates "stash@{", but the second one
generates curly braces, the third one does the same, and so on ad
infinitum.

I didn't specify file (-f) or any special completion, so why would zle
attempt curly brace expansion, especially if the words contain curly
braces, and the current character is a curly brace?

Here's a simple test:

----------------------------------------
#compdef foo

_foo () {
compadd -Q -- 'stash@{0}' 'stash@{1}'
}

_foo
----------------------------------------

Cheers.

-- 
Felipe Contreras