<Esc> exit insert mode functionality blocked by autocomplete tab stops about vrapper HOT 8 OPEN

Sever years and counting, since last message. Could anyone find a resolution for this annoying problem?

from vrapper.

Personally, I think this is the single most annoying thing about Vrapper. It bothers me on a daily basis. However, we haven't found a single workaround for it.

The root of the problem is that Eclipse receives all key presses first and only passes them down to Vrapper if nothing is defined for that key. Fortunately, Eclipse allows you to unbind most Ctrl keys in the preferences, which allows Vrapper to receive those Ctrl key presses. Unfortunately, Eclipse doesn't allow you to unbind . So when Eclipse goes into autocomplete (SmartInsert) mode and you hit it exits that mode and doesn't bother telling Vrapper that you did anything.

I would be happy with either of your proposed solutions. However, since Eclipse doesn't tell us when it enters or exits SmartInsert mode, we can't do anything about it. I've gotten into the habit of hitting 3 or 4 times in a row when I see Eclipse go into SmartInsert mode. If you can find any solution for this please let us know, I'm afraid we've made no progress so far.

from vrapper.

Man what a pain :) Thanks for the details. If I do happen to come across a solution to this I'll definitely pass it your way.

from vrapper.

I'll close my issue since it's discussed here. What's weird is that it seems to work fine on my OracleLinux5.6 (exactly the same as RedHat) box. But on my Windows 7 and CentOS 6.2 boxes is closes perspectives.

On a sidenote viable hasnt worked on any of the ~7 or 8 different os's ive tried it on.

from vrapper.

Since I keep referring to this defect from other defects, I should probably list the only known workaround I'm aware of. Some people like remapping the key to some other key combination (like 'jj' or 'jk') so their fingers never need to leave the home row of their keyboard. If you do this, the mapping will be performed as you expect and you won't have to be caught up in the battle between Vrapper and Eclipse for use of your key.

from vrapper.

+1 for initial suggestion. Shame about the unsolvable dilemma. Any chance this could get brought to the attention of the Eclipse developers? Seems like the only solution would be for them to implement appropriate event hooks for SmartInsert mode...

from vrapper.

Wasn't this issue solved when #156 got implemented?

from vrapper.

No, this still happens for me. When Eclipse goes into the autocomplete mode for filling out method arguments, it draws boxes around each method argument, displays the content assist menu for the first argument, and displays a tooltip above the line showing you the object type of each argument.

Hitting <ESC> once removes the tooltip above the line, hitting it again removes the content assist menu, then hitting it a third time actually exits the autocomplete mode and returns Vrapper to NormalMode. It's possible we now only have to hit <ESC> three times rather than four, but it's still annoying.

from vrapper.