Bug: Plain-Text Completion Triggered by Non-Matching Char about viasfora HOT 5 CLOSED

I have this issue happening all the time with resharper intellisense enabled instead of VS intellisense.

The resharper intellisense comes up, then viasfora overlays on top of resharper for the first n entries. Resharper's first n entries are not necessarily viasforas first n entries. Tabbing out a selection is selecting the resharper entry while the viasfora entry was the visible entry quasi selected.

Clicking escape when both intellisenses are open up closes resharper intellisense while viasfora intellisense remains open.

from viasfora.

This is because Resharper is very heavy handed.... it basically takes over all VS-provided completion and then screws up anything else working there.

You can just disable Viasfora's plain-text completion from the options dialog (seriously, every single feature can be independently turned on/off, not sure why people don't notice. Should I make it more visible somehow?)

from viasfora.

You are too quick! I just found the option to disable the Plain-Text Completion. I disabled many other addons and resharper extensions trying to figure out what was conflicting. Never guessed it was a viasfora, I did not notice the Plain-Text Completion in the last update. Note if I disable resharper intellisense, I had no issues with Plain-Text Completion at all (thus hitting the resharper extensions as the conflict option).

Thanks for the option to disable Plain-Text Completion, so I do not have to choose what to live without. Really can not live without the the rainbow braces anymore.

from viasfora.

What I tried to do when I implemented Plain-Text Completion was try to figure out if someone else had a completion session active, and avoid popping up the viasfora one. In most cases, that works just fine, because the language-provided completion usually comes up first (it's not perfect, but it's the best compromise I could come up with at that time).

I'm not quite sure how Resharper hooks into the process, and so how exactly it comes up might depend on the order in which the command handlers are inserted (just guessing, really).

I've been tempted to completely disable automatic popup of plain-text completion and even not handling the complete-word command, and instead use some other means of starting the plain-text completion session (maybe some particular key combination) but.... that would make it far less useful :/

from viasfora.

I've now changed this so that only an explicit Tab/Enter key will commit the selected completion.

from viasfora.