-
Notifications
You must be signed in to change notification settings - Fork 20
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
Flickering with deoplete #71
Comments
@rgrinberg: Thanks for opening this issue, I've had noticed similar problems myself before. Usually it is related to gathering candidates, especially if you have many tmux sessions and windows open, it can take a noticeable time to process all visible words. There are already some settings g:tmuxcomplete#capture_args
g:tmuxcomplete#list_args which can be used to control which sessions, windows and what scrollback to consider. I think most of these issues could be resolved by limiting the search space used for live autocompletion. For on demand completion a slightly longer delay is usually acceptable, that's why this wasn't always a priority. Unfortunately these settings are currently not documented and I take this issue as motivation to do that. I'm planning to include some best practices to help with issues like the one you're seeing. Unfortunately I can't promise that I'll come to this soon, but I'll definitely put it on my list 👍 Side note: Maybe it's even possible to do all that processing in the background with Neovim, but I'm not too familiar how that would be done. If anyone would have some pointers that might give me a head start. |
This may have been alleviated by Shougo/deoplete.nvim@2f6f7b9 @rgrinberg Can you confirm/deny? |
I am using Profiling shows this:
I could imagine that it would be better already when And then it's also a matter of configuration probably: I would like to use the tmux completion on demand only, and not on-the-fly all the time. |
When used in conjunction with deoplete I get constant cursor flickering. This flickering disables when I disable tmux-complete so I'm pretty certain this plugin is the cause of it. I'm wondering why tmux-complete causes this however, is it because gathering candidates is slow?
The text was updated successfully, but these errors were encountered: