Occasionally lusty-explorer breaks and stops displaying lusty completion window

[stsquad]

I'm not sure how I'm triggering this yet but there have been a couple of times when lusty gets broken. Will the mini-buffer presents the usual prompt there is no longer a completion buffer.

How do I get the completion buffer to re-appear? Is it not dynamically created when needed?

[sjbach]

Hi, I've seen this happen a couple times too. Not sure what's causing it, but I will investigate.

[sjbach]

This just happened to me again for the first time this month - haven't yet established the cause or determined a fix, but it seems like lusty-explorer only becomes broken for a specific buffer. So as a workaround, if you create a new buffer (or switch to another buffer) and launch from there, the explorer works fine again. It'll continue to be broken on the first buffer, but you can kill it and reopen.

Unfortunately this is difficult to reproduce, so can't say when a fix is forthcoming.

[sjbach]

I've also seen this being caused by what appears to be a bug in Emacs. It gets into a state where it no longer calls the functions listed in post-command-hook during read-buffer or read-file-name.