Skip to content
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

Looking for maintainers #33

Open
kzkn opened this issue Aug 7, 2023 · 3 comments
Open

Looking for maintainers #33

kzkn opened this issue Aug 7, 2023 · 3 comments

Comments

@kzkn
Copy link
Member

kzkn commented Aug 7, 2023

Hi all,

I am currently an active rufo maintainer. However, I am not a vim user and will not maintain this package. Nevertheless, I don't think it is desirable for this package to be left as it is. Is there anyone who can take over?

Or, I would be happy to suggest some good ways of integrating Rufo and Vim. It does not necessarily have to be a dedicated package like rufo-vim, but I think there are ways to ride on a more generic package. For example, in Emacs, rufo could ride on reformatter.el.
If it is good enough, put it in rufo's README. Then rufo-vim can finish its job.

Thanks.

@lucerion
Copy link
Member

lucerion commented Aug 7, 2023

Hi @kzkn,

I don't understand a little bit what do you mean by generic package... Is it something like existing solution that will use "rufo as backend"?

@kzkn
Copy link
Member Author

kzkn commented Aug 7, 2023

 Is it something like existing solution that will use "rufo as backend"?

Yes

@lucerion
Copy link
Member

lucerion commented Aug 9, 2023

Formatters in vim are also plugins. There is no one plugin that most people use. They are often written for one language. One of the plugins that can use external programs for formatting is ale. You can already use rufo with it. You have to remember that such plugins are limited, while this plugin has a wide range of features and is usable except for bugs.

I think we have two cases here 1) find a maintainer for this plugin 2) wait while someone add support rufo to other plugins (like in ale). The second way is long and doesn't promote rufo, as for me. On the contrary, rufo should be popular so that someone adds it to other plugins.

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

No branches or pull requests

2 participants