On windows, I found sometimes the completion couldn't be shown
Clang completion buffer keeps flushing
After enabled some "message" traces, I found Message buffer keeps showing
"ac-clang-candidate triggered - fetching candidates..."
Then the ac-clang-candidate is somehow called again and triggered ac-clang-filter-output again...
This makes a infinite loop and stops the completion working.
I'm able to work around by remove that setq line, not sure how the nature of the problem should be though.
On windows, I found sometimes the completion couldn't be shown Clang completion buffer keeps flushing After enabled some "message" traces, I found Message buffer keeps showing "ac-clang-candidate triggered - fetching candidates..."
More debugging shows that somehow after the status set to idle in ac-clang-filter-output at:
Then the ac-clang-candidate is somehow called again and triggered ac-clang-filter-output again... This makes a infinite loop and stops the completion working.
I'm able to work around by remove that setq line, not sure how the nature of the problem should be though.
Environment: win7+emacs24.3(official binary)+auto-completion1.3.1