Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I've only been skeptical, I didn't reject the idea. If you read my very first comment in the thread were you suggested adding the package to ELPA, I wrote that I already had considered it. So I think nothing has really changed. I had to test first how the ELPA workflow works, which I did with my Vertico and Corfu packages. After that went positive, there was no strong argument to not make the move. Initially I was hesitant since ELPA requires the assignment, I didn't have it at that time and I wasn't yet sure about the direction Consult was taking. It could have been that Consult would have been much more of a kitchen sink with many contributors, accepting more controversial commands. But then I concluded that it is better to keep Consult somehow focused (it still is a kitchen sink!), and keep wider functionality in external packages to help with the modularity. This is mainly thanks to /u/purcell who convinced me to not throw everything together in a single consult.el file, when I added consult-flycheck, which lives now in its own repository outside ELPA.
Consult is a collection of useful navigation and search commands based on completing-read, compatible with various completion UIs. Marginalia enhances completion commands with informative annotations in the minibuffer.
I've only been skeptical, I didn't reject the idea. If you read my very first comment in the thread were you suggested adding the package to ELPA, I wrote that I already had considered it. So I think nothing has really changed. I had to test first how the ELPA workflow works, which I did with my Vertico and Corfu packages. After that went positive, there was no strong argument to not make the move. Initially I was hesitant since ELPA requires the assignment, I didn't have it at that time and I wasn't yet sure about the direction Consult was taking. It could have been that Consult would have been much more of a kitchen sink with many contributors, accepting more controversial commands. But then I concluded that it is better to keep Consult somehow focused (it still is a kitchen sink!), and keep wider functionality in external packages to help with the modularity. This is mainly thanks to /u/purcell who convinced me to not throw everything together in a single consult.el file, when I added consult-flycheck, which lives now in its own repository outside ELPA.
I've only been skeptical, I didn't reject the idea. If you read my very first comment in the thread were you suggested adding the package to ELPA, I wrote that I already had considered it. So I think nothing has really changed. I had to test first how the ELPA workflow works, which I did with my Vertico and Corfu packages. After that went positive, there was no strong argument to not make the move. Initially I was hesitant since ELPA requires the assignment, I didn't have it at that time and I wasn't yet sure about the direction Consult was taking. It could have been that Consult would have been much more of a kitchen sink with many contributors, accepting more controversial commands. But then I concluded that it is better to keep Consult somehow focused (it still is a kitchen sink!), and keep wider functionality in external packages to help with the modularity. This is mainly thanks to /u/purcell who convinced me to not throw everything together in a single consult.el file, when I added consult-flycheck, which lives now in its own repository outside ELPA.
I've only been skeptical, I didn't reject the idea. If you read my very first comment in the thread were you suggested adding the package to ELPA, I wrote that I already had considered it. So I think nothing has really changed. I had to test first how the ELPA workflow works, which I did with my Vertico and Corfu packages. After that went positive, there was no strong argument to not make the move. Initially I was hesitant since ELPA requires the assignment, I didn't have it at that time and I wasn't yet sure about the direction Consult was taking. It could have been that Consult would have been much more of a kitchen sink with many contributors, accepting more controversial commands. But then I concluded that it is better to keep Consult somehow focused (it still is a kitchen sink!), and keep wider functionality in external packages to help with the modularity. This is mainly thanks to /u/purcell who convinced me to not throw everything together in a single consult.el file, when I added consult-flycheck, which lives now in its own repository outside ELPA.