-
Notifications
You must be signed in to change notification settings - Fork 40
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
Is this project still active? #83
Comments
Active? no. Abandoned? also no. It's been a bit over a year since I made the first commit to the repo, and in that time I've actually learned a lot about Neovim and package management in general. I've been wanting to write a small post about the things I learned, and about when I should consider Paq “complete”. I just haven't had the time for it. For now, like you said: it mostly works 🤷. |
@savq I subscribed to this issue. If you post your blog post let us know by linking it here so we get a notification. |
I decided to make a 1.0 release so that people know the current features are mostly stable and won't change in the near future. I also added a bug report template. Hopefully I'll be able to fix bugs in a more timely manner. |
@danshumaker I'll probably won't add your suggested feature, but you might be able to achieve something similar using autocommands. like: autocmd User PaqDoneSync PaqLogOpen |
I'll close this since the answer for the past 2 years has been "Yes. It's active, but not much." Near future developments are tracked in #149 |
Hello, I use
Paq
and I have no complaints: it does everything I need, I think that it is amazing.Nonetheless, I wonder if it is/will still be active.
Best wishes
The text was updated successfully, but these errors were encountered: