Skip to content
This repository has been archived by the owner on Aug 11, 2024. It is now read-only.

Glepnir came back #123

Open
pedro757 opened this issue Jun 25, 2022 · 3 comments
Open

Glepnir came back #123

pedro757 opened this issue Jun 25, 2022 · 3 comments

Comments

@pedro757
Copy link
Contributor

Now that glepnir came back what are you going to do? What will be the future of this project? I'm just curious

@kkharji
Copy link
Owner

kkharji commented Jun 25, 2022

hey @pedro757, great question, the project started as something to fill the void @glepnir left when he unfortunately had a health issue. So it started as a fork to be maintained with support of neovim nightly. There was some features here and there that I hope @glepnir have seen, but mostly bug fixes. Now that our dear @glepnir is back, I personally, using this fork out of laziness or perhaps not being able to switch at this time.

What will be the future of this project?

I guess most likely it will be archived, perhaps in few months as I find time to transition and start testing and adapting to @glepnir's new version.

Does this answer your question? also, you have anything in mind feel free to share.

@jinzhongjia
Copy link

Please keep this fork, because the user experience maintained by glepnir is not as good as the current one, at least for me, because it adds some features I don't need, and it's not very easy to use

@kkharji
Copy link
Owner

kkharji commented Sep 30, 2022

@jinzhongjia interesting. I'm still using this fork. I haven't got the time to switch yet. I'm a bit shocked that glepnir maintained version evolved to have totally different user experience. No worries, even if I switch, I will keep this fork 👍🏻

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants