-
Notifications
You must be signed in to change notification settings - Fork 15
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
Weird behavior inside GUI (neovide) #118
Comments
Thanks for reporting this. I have not worked with any Neovim GUI so far so never configured the plugin for it. I'll check this out. |
Worked around it by setting: client_callback = function(port, _)
local cmd = ("neovide --server localhost:%s"):format(port)
vim.fn.jobstart(cmd, {
detach = true,
on_exit = ...
})
end, |
Awesome. That's how I drive my personal set up too. I have a PR open to fix part 1 of your issue. I have squashed one bug that might have been leading to 2 and 3, but not sure if your issue got fixed. Let me know if it is not. |
Hey, let me know if you are still seeing any issues in Neovide or otherwise. |
Going ahead and closing this. If you or anyone else still faces issue mentioned here, please re-open this or create a new issue. |
Hi @amitds1997, sorry for disappearing. I actually stopped using neovide with remote-nvim, since it was less convenient than tmux+TUI (I wanted persistent terminals in the remote host). I didn't test the default behavior after your change because the custom client command worked perfectly. If you want I can play around with the latest version. Thanks! |
Hey, no worries. As long as it works for you, that's great. If anyone else faces any such issue, they'll open a new issue. Thanks! |
Bug description
I tried using the plugin in neovide, and it generally worked, but had some issues.
To reproduce
Steps to reproduce the behavior:
neovide
RemoteStart <host>
, with a host with the client-auto-connect option turned on.Expected behavior
System info
The text was updated successfully, but these errors were encountered: