mhinz / neovim-remote

:ok_hand: Support for --remote and friends.
MIT License
1.73k stars 83 forks source link

is this project alive? #169

Closed gigatexal closed 2 years ago

gigatexal commented 3 years ago

Is this project still active? Do you want help maintaining it?

ashishbinu commented 3 years ago

Last commit was two years ago. Seems like no one is maintaining it now.

Shougo commented 2 years ago

I want to maintain the project.

Shougo commented 2 years ago

Fortunately, I know both Python and neovim/Vim implementation.

fwsmit commented 2 years ago

I think we need a fork here. The maintainer doesn't seem to be active anymore.

Shougo commented 2 years ago

Oh... OK. I will fork it. I have seen him in gitter though.

https://github.com/Shougo/neovim-remote

Shougo commented 2 years ago

I accept PRs in forked repository instead.

Shougo commented 2 years ago

You should use neovim native remote feature instead.

https://github.com/neovim/neovim/pull/17439

fwsmit commented 2 years ago

You should use neovim native remote feature instead.

neovim/neovim#17439

Oh cool!

Shougo commented 2 years ago

Some features is not implemented, but the official is important.

sisrfeng commented 2 years ago

How to install the alive version of nvr? I prefer standalone nvr to nvim nightly. @Shougo

Shougo commented 2 years ago

Nothing alive version unfortunately. I think to improve built-in remote feature is better.

You can install neovim-remote from github by pip command.

pip install git+https://github.com/Shougo/neovim-remote
sisrfeng commented 2 years ago

Sad to find there is little update in the forked one:
The only changed part: image

(https://github.com/Shougo/neovim-remote)

fwsmit commented 2 years ago

What's wrong with the new built in nvim remote?

sisrfeng commented 2 years ago

It lack some features, which can be found in this repo But this repo seems to cause crash if I load 50+ files in the buffers. (not sure)

fwsmit commented 2 years ago

I'd suggest opening an issue at nvim mentioning the missing feature(s) that you need. Don't expect too much development here or at the fork, except if you're submitting it yourself. Most people decided it was best to use the nvim native version.

Shougo commented 2 years ago

Yes. The native implementation is better. I have changed neovim-remote only I needed one. It is already maintenance mode.

Shougo commented 2 years ago

I need the PR feature.

https://github.com/neovim/neovim/pull/17856

Why do you need to use neovim-remote? I think current neovim remote feature is not same.

sisrfeng commented 2 years ago

I need the PR feature.

neovim/neovim#17856

Why do you need to use neovim-remote? I think current neovim remote feature is not same.

You mean we should use the built-in --remote, instead of this repo? But I have something like this: alias ed='\nvr -d -c "wincmd h" -c "diffthis"' alias e='nvr -cc tabedit -c "tabmove -1"'

But

image

Shougo commented 2 years ago

You mean we should use the built-in --remote, instead of this repo?

Yes. Because the repository is not maintained anymore.

Oh, if +cmd is needed for me.

Shougo commented 2 years ago

I have checked current remote feature in neovim. wait variants and +cmd support is only needed.

sisrfeng commented 2 years ago

Thx.

I have checked current remote feature in neovim. wait variants and +cmd support is only needed.

You mean that wait variants and +cmd support are the only missing part in official nvim, and we need to want for them to be implemented? (Sorry, I'm not a native speaker for English)

Shougo commented 2 years ago

You mean that wait variants and +cmd support are the only missing part in official nvim, and we need to want for them to be implemented?

Yes.

mhinz commented 2 years ago

It's still alive. ;-)

Shougo commented 2 years ago

Thanks. If the project still alive, can you include the changes or why shortmess is ignored?

https://github.com/mhinz/neovim-remote/pull/154

sisrfeng commented 1 year ago

To anyone new to this issue (and my future revisiting): After this: image

The fork seems dead now: image ... image

Shougo commented 1 year ago

The fork is dead now. Because the project is alive. (The development is slowly though)