-
Notifications
You must be signed in to change notification settings - Fork 35
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 help with Bullets.vim #126
Comments
I would really like to help out, though I feel I will not have the time to be a full time maintainer either. If you make me a contributor, I could probably handle a large fraction of PRs and other issues. If it seems like it is going well I can take over as maintainer. |
@harshad1 Thank you for offering to help! I just moved the repo to a separate org and sent you an invite to join as a collaborator :) |
|
Are you asking how to install and use vim bullets? |
I mean the lua version of bullets ^_^,if it was exist |
Currently, bullets.vim does not auto-continue the > blockquote symbol when pressing Enter in Markdown. It would be great if the plugin could automatically add > at the beginning of the next line, similar to how it handles list items. Thank you! |
I slapped together a neovim lua version of this plugin a while ago. It's not really in publishable shape as there is no readme or documentation, but it generally works similarly to this plugin. https://github.com/kaymmm/bullets.nvim |
okey, thanks |
Hi everyone,
First, please accept my apologies for not maintaining this plugin more actively. I know there have been some open issues and pull requests going stale and those should definitely have been addressed, but I simply didn't have the time.
When I wrote this plugin about 7 years ago, it was done for a meetup talk about how to write a vim plugin. I had read the book Learn VimScript The Hard Way by Steve Losh and wanted to use teaching as a learning opportunity.
I never really thought this plugin would gain as much traction as it did, but it still continues to grow to this day with downloads and really awesome additions from the community.
My priorities have changed since switching to Neovim. While this plugin works just fine in Neovim, I am now fully invested in Lua and no longer interested in writing VimScript. I thought of rewriting it in Lua, but frankly I don't have time for that at the moment.
If anyone is interested in taking over maintenance please let me know by posting below. I'll be happy to set up a call and give you a tour of how it's built, goals vs non-goals, and how to best maintain it going forward. I might also be available for some pairing sessions to help get you started on some much needed improvements.
I want to make sure whoever maintains it next has a great developer experience and that it is in good hands.
The text was updated successfully, but these errors were encountered: