Cursor movement slow/laggy when semicolon present in Vi mode
See original GitHub issueDescription
Moving around a multi-line query to edit it is extremely slow+laggy in Vi mode when a semicolon is present at the end of the line. Deleting the semicolon instantly speeds up movement for some reason. This is obnoxious in multiline mode when a semicolon is required to send a query and when one wants to move up to edit the query.
Your environment
- Please provide your OS and version information. MacOS 10.14.2
- Please provide your CLI version. 2.0.2
- What is the output of
pip freeze
command. Empty for some reason
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Moving cursors down in visual mode is laggy : r/neovim - Reddit
Whenever I use visual mode moving cursor down has noticable delay. I didn't map 'j' for anything in visual mode.
Read more >VIM Cursor Movement Latency on macOS · Issue #506 - GitHub
When I open a 200 line text file with nvim , and hold down h/j/k/l to move the cursor over extended number of...
Read more >Emacs point(cursor) movement lag
I have found an answer to my question through narrowing down the naughty bit and googling. I have managed to reduce the lag...
Read more >Returning insert mode cursor to same place after function call
The problem I am having is when calling this function on the last column, you have to exit insert mode to call this...
Read more >vi Tutorial - SoftPrayog
When a cursor movement command is given alone, by itself, it results in movement of the cursor from one location to another in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should be fixed on master due to #1109 - @isobit’s analysis was spot-on - we were unnecessarily calling the expensive
is_open_quote
method (way) too frequently due to the way the multi-line mode was being switched on/off dynamically. Now, we only run that method once, on Enter keypressFixed in 2.2.0.