-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Deferred Clipboard only kicks in after focus is lost at least once #2
Comments
I'm glad it's useful for you! So do you still want to use the fallback in case of clients that do not have support for change events? I believe it's not possible until support for focus change events is truly detected - as any of them fire the first time. If you don't care for fallback just leave |
Would it be possible to check the availability of the Focus changed events using something like local hasFocusEvent = vim.api.nvim_command_output(([[echo exists('##FocusLost')]])
if hasFocusEvent == '1' then
vim.o.clipboard = nil
end This should cater for the fallback as the exists command returns only if the client supports the provided command |
It seems to always return EDIT: Submitted additional issue here: neovim/neovim#21655 |
Let's keep the issue open as the issue still stands. Maybe there is still a better solution for it. |
Ah thats an oversight on my part, the Hopefully there is a smarter way to defer the clipboard on startup as its definitely something I find useful. Thanks again! |
Due to syncing Windows and WSL via win32yank.exe, there is a notable lag when copying thing to the clipboard and on WSL, I see a massive improvement in performance when using this plugin! Thank you.
The issue I have is when I open Neovim for the first time, I don't see this performance boost until I at least lose focus once.
I believe its due to the fact that
schedule_disable_of_continuous_clipboard_sync_on_focus_change
only triggers thevim.o.clipboard = nil
after eitherFocusGained
orFocusLost
Is it possible to call this earlier in the setup to make the performance boost immediately available rather than having to trigger a
FocusLost
manually each timeThe text was updated successfully, but these errors were encountered: