-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lag when inserting before of after a block selection #6
Comments
Yes I see. That is because of the visual mode mappings beginning with |
Is there a use case for having visual mode mappings? |
Well usually all text objects work both in visual and operator pending mode. So you could visually select an area and possible change it before applying your operator. But the visual mode mapping is certainly not as important as the operator pending mode one. And appending after a visual block mode selection is definitely more important than my mappings. So as a last resort I could just remove the visual mode mapping. But before I do that I would like to investigate if there is any way to have the mapping only kick in when in visual mode, but not when in visual block mode. |
Unfortunately there doesn't seem to be a way to have a mapping only in visual, but not in visual block mode. It might be possible to create and delete these mappings every time visual block mode is entered and left, but that seems too dirty in comparison to the gained benefit. |
There is a noticeable lag that this plugin introduces when inserting before or after a block selection.
To reproduce create a file like this:
Visually select all the = signs, execute shift+A. There is a noticeable lag before it drops you into insert mode.
Is there any possibility of reducing or eliminating this lag?
The text was updated successfully, but these errors were encountered: