-
Notifications
You must be signed in to change notification settings - Fork 61
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
Blinking cursor , flashing f^[ #2
Comments
I installed spf13 but unfortunately I was not able to reproduce the blinking. Background: Could you please test the following?
and wrap it the following way, so that 'showcmd' is temporarily disabled while feeding 'f\e':
Does it solve the problem? |
Unfortunately it does not: http://ge.tt/7aqjh681/v/0?c However i just now noticed that it does it in other buffers as well. I'm working from a fresh spf13 as well, so it's strange it won't duplicate on your setup. I'm on mountain lion, using iterm2 with zsh, though it does the same thing in macvim, so i'm assuming it's not a problem with my terminal session. Maybe slowing down the timer? |
Then it may be related to the speed of the terminal.
If this still does not help then please redo your test with 'showcmd' just completely turned off in vim. |
That works just fine, however the cursor is still blinking incredibly fast, it is much slower in macvim, so you are right about how fast the terminal is, any idea how to correct? |
Please check the value of 'updatetime' and g:slimv_updatetime. The timer uses these settings for the re-trigger frequency (especially the second one during REPL refresh mode). Some notes on the original issue: |
updatetime=4000 Mainly it was the speed at which it was happening which caused the problem, very distracting blinking and putting the key combo there in the corner of my eye. So it's not as big of an issue if i can get it to slow down. I know i can check something by 'set updatetime?' however that doesn't work for g:slimv_updatetime , how do check the current value? And thank you for all the help. |
You check options by 'set option?' and you check variables by 'echo variable'. set updatetime? The latter one is 500 (=0.5 sec) by default. Please check (during your test) this: :au CursorHold Does it print anything else than a single line of "* :call SlimvTimer()"? BTW, does the whole problem happen without spf13? |
Well after removing spf13 there was no problem, so it is definitely a conflict with spf13 that causes this, i'll get back with you after figuring out what conflicts. Results of :au CursorHold
The problem is gone after removing the tagbar plugin. Should I open an issue with them, or shall we look at what their code is doing? |
Thank you, that was a great help! Let's try to identify the real root of the problem before opening an issue for another plugin, because it is possible that it's really slimv's fault. I tried to check the code of the tagbar plugin, and I have some ideas.
If this does not help then I think we should find the exact autocommand(s) of tagbar that interfere(s) with slimv. (1) tagbar/autoload/tagbar.vim, line 967:
(2) tagbar/autoload/tagbar.vim, lines 984-985:
(3) tagbar/autoload/tagbar.vim, lines 968-969:
(4) tagbar/autoload/tagbar.vim, lines 975-978, :
Sorry for adding so many tasks, I would do them myself if I could reproduce the problem. :( |
augroup did not solve problem
When opening vim and :e myfile.lisp It is hit or miss as to whether there is a problem New theory emerged: I have yet to get it to reproduce glitch while providing the file to be edited from shell, also i have noticed that the Airline plugin glitches out when i open .lisp files from inside vim (no other file type) causing the status bar to be blank. Short video demonstrating the above: http://ge.tt/1jQ0wQ81/v/0 The following are the only lines in my .vimrc.local file that deals with lisp augroup ft_lisp
au!
"Lisp no auto close
au FileType lisp let b:AutoClosePairs = AutoClose#ParsePairs("\" ()")
au FileType lisp let b:paredit_electric_return=0
augroup end Is there a different start up order when file is opened from command line vs in vim?
There must be something different about the way it handles things when you open a file different ways. |
Didn't realize i had closed this |
Thanks for the detailed test report. TBH I'm a little clueless. :(
(1) What happens if you comment out this line in function SlimvTimer() in slimv.vim?
This way there will be no buffer switch, only CursorHold will be re-triggered. (2) What happens if you comment out the 'call feedkeys(...)' lines in SlimvTimer(), but keep 'call SlimvRefreshReplBuffer()' uncommented? As a final resort we can enable vim's verbose logging:
Please send me the resulting 'test.log' file (you can find my email address in the slimv doc). |
Commenting out "call SlimvRefreshReplBuffer()" in SLimvTimer() removed the problem, I went ahead and put it back in and sent the test.log file for greater insight in to the problem. Also following your second step commented out the feedkeys, leaving in the call to SlimvRefreshReplBuffer() also fixes the problem |
Hi team. Is there a solution for the problem now? I am still experiencing this. As it eats my :verbose au CursorHold
--- Auto-Commands ---
gitgutter CursorHold
* call gitgutter#process_buffer(bufnr(''), 1)
Last set from ~/.dotfiles/vim/.vim/plugged/vim-gitgutter/plugin/gitgutter.vim
CursorHold
* unlet! b:airline_head
Last set from ~/.dotfiles/vim/.vim/plugged/vim-airline/autoload/airline/extensions/branch.vim
airline_whitespace CursorHold
* call <sid>ws_refresh()
Last set from ~/.dotfiles/vim/.vim/plugged/vim-airline/autoload/airline/extensions/whitespace.vim
SlimvCursorHold CursorHold
* :call SlimvTimer()
Last set from ~/.dotfiles/vim/.vim/plugged/slimv/ftplugin/slimv.vim |
Unfortunately I was (and still am) unable to reproduce the problem. I'm pretty sure it's somehow related with the interaction of the various |
By commenting out Anyway I am glad to help if you want to hunt down this bug.
|
OK, thanks, so the problem seems to be that the |
I indeed manually set it in Another interesting observation during my experiment is that Thank you for the insightful suggestion on |
I did some changes, I'd like you to check it out. It should address two problems: (1) recognize changes done to
|
It saves and loads correct |
OK, thanks, I committed these changes. Do you still have the blinking? Can it be solved by increasing |
I unset |
Video of bug http://ge.tt/1tgt4481/v/0?c
Using spf13 + slimv
Steps to reproduce:
Start vim
edit a .lisp file
,c to start swank
cursor begins blinking with f^[ being flashed in the bottom
The text was updated successfully, but these errors were encountered: