You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! While I am not an active user of spacemacs, it has come to my attention that it ships with sabof's org-bullets. I am the current maintainer of the MELPA fork, which has diverged from the main code with a variety of patches in the past 6 years. For that reason (and to avoid a duplication of effort) I've come here primarily to ask whether you would like to use my fork of the package instead, which is my first step towards trying to unify the user experience of the package across Emacs distributions. But why do I say "primarily"? Well... I think I should give a bit of context for that.
The package org-bullets, while immensely popular with over 600k downloads on MELPA, has matured enough that I would personally consider any major changes to it hard to justify towards the end-user. This, combined with the fact that to my knowledge several versions of this package already exist, led me to the decision that it would be best to "freeze" the package, only applying bug fixes and general maintenance to keep it running, not create further divergence among packages of the same name.
However, that begs the question: what to do with existing feature requests that never ended up in the package? What with features I myself would have liked to see? Enter org-superstar, a package I have written from scratch after a thorough dissection of org-bullets. While it has taken ideas from org-bullets, it shares no code with it, and extends the ideas of org-bullets, and can emulate its function, making it more of a spiritual successor than a fork. Consequently, it is still very much active and subject to change (although it is mature enough that I will not break backwards compatibility with older versions of itself without warning). Superstar seems to do quite well, too: it already reached over 17k downloads on MELPA in roughly half a year since its inception.
Which finally brings me to my second suggestion: Would you be interested in replacing org-bullets with org-superstar?
So to summarize, would you be interested in
changing your upstream repo for org-bullets to the MELPA one for a more unified user experience, or
replacing the package with a successor package (org-superstar) offering some additional bells and whistles?
I'll gladly go into more detail about the differences between the two packages, if need be.
The text was updated successfully, but these errors were encountered:
Ah, awesome! 🥳 I tried to make the transition from Bullets to Superstar as painless as possible, but should you come across something bothersome I have overlooked be sure to let me know.
Hello! While I am not an active user of spacemacs, it has come to my attention that it ships with sabof's org-bullets. I am the current maintainer of the MELPA fork, which has diverged from the main code with a variety of patches in the past 6 years. For that reason (and to avoid a duplication of effort) I've come here primarily to ask whether you would like to use my fork of the package instead, which is my first step towards trying to unify the user experience of the package across Emacs distributions. But why do I say "primarily"? Well... I think I should give a bit of context for that.
The package
org-bullets
, while immensely popular with over 600k downloads on MELPA, has matured enough that I would personally consider any major changes to it hard to justify towards the end-user. This, combined with the fact that to my knowledge several versions of this package already exist, led me to the decision that it would be best to "freeze" the package, only applying bug fixes and general maintenance to keep it running, not create further divergence among packages of the same name.However, that begs the question: what to do with existing feature requests that never ended up in the package? What with features I myself would have liked to see? Enter org-superstar, a package I have written from scratch after a thorough dissection of org-bullets. While it has taken ideas from org-bullets, it shares no code with it, and extends the ideas of org-bullets, and can emulate its function, making it more of a spiritual successor than a fork. Consequently, it is still very much active and subject to change (although it is mature enough that I will not break backwards compatibility with older versions of itself without warning). Superstar seems to do quite well, too: it already reached over 17k downloads on MELPA in roughly half a year since its inception.
Which finally brings me to my second suggestion: Would you be interested in replacing org-bullets with org-superstar?
So to summarize, would you be interested in
org-bullets
to the MELPA one for a more unified user experience, ororg-superstar
) offering some additional bells and whistles?I'll gladly go into more detail about the differences between the two packages, if need be.
The text was updated successfully, but these errors were encountered: