-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Permit setting firenvim to use --remote
instead of starting a new neovim instance
#197
Comments
Yes, it should be possible to implement something like I'm disappointed to hear that startup is slow for you though and this is something I will fix regardless of whether and when |
Work has started in the impl_single_server branch and is blocked by neovim/neovim#11646. |
Now blocked by neovim/neovim#3338. |
neovim/neovim#11331 was merged. Closing neovim/neovim#3338 |
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Currently buggy if `:qall!` is used. Closes #197
Now implemented on master, either build from source or wait for a new release. See this section of the readme to learn how to use it :). |
Does it require neovim built from neovim/neovim#11821 at least(i.e. any commit since this was merged)? |
Yep, that's what I mean by "this requires a Neovim compiled at commit a2efc9c or more recent." :) |
idk why, the way I read it, I wasn't sure if this was referring to firenvim or nvim. Anyway, as long as you're not using the persistent server, you're fine right? |
Yep, should be (except for #428 which I intend to fix ASAP). |
Could a way of using nvr be set up, so that each new firenvim instance connects to an existing neovim process rather than having to start up a new instance?
Neovim isn't always instant to start, especially if configured for more ide-like editing. I'm very pleased that I can use vim to edit jupyter notebooks properly now - but starting a new editor instance every time I click a box is painful. Connecting to a server would salve this.
The text was updated successfully, but these errors were encountered: