-
Notifications
You must be signed in to change notification settings - Fork 83
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
Different command for nvr #48
Comments
I totally see the need for customizing the command used by nvr. Using an environment variable for it also makes sense in this case. Adding env var support just for silent mode seems a bit overkill to me though. :-) So, how does support for |
sounds good to me :) P.D. silent mode, can we see this in another issue ? |
Why do you need that as env variable if |
Oh, ah. Yes.. But |
The above commit should make |
-s works, but now neovim-remote launch a new nvim console every time, saying that can't connect to /tmp/nvimsocket ... $NVR_CMD set to nvim and neovim-gnome-wrapper, same scenario :( |
Does |
my mistake, I quit neovim and after this /tmp/nvimscket remains, so I delete the socket, restart with nvr -s and it works! |
Oh, usually nvim should remove the socket on its own, except when it got killed. Anyway, I guess this can be closed now? |
yes :) close this one ... thanks! P.D. one last thing, add the $NVR_CMD info in the README.rst file. |
Done. Thanks for bringing up all these issues! |
I had configured neovim in my machine (Ubuntu 16.04 LTS) with neovim-gnome-terminal wrapper, to have a 'gui' for me.
now, I see that neovim-remote call directly 'nvim' (line 78 in
nvim/nvim.py
file).can be possible to setup this command with an ENV var for example ? In my case I have 'neovim' command in my path (that call neovim-gnome-terminal wrapper' and I change in this line to 'neovim' command and works.
this can be an ENV variable that if is setup can be used and if is not, we use
nvim
commandthe same thing can be for silent mode, that can be default if an ENV var is setup too.
The text was updated successfully, but these errors were encountered: