From: D <d.williams@posteo.net>
To: Jonas Bernoulli <jonas@bernoul.li>, emacs-orgmode@gnu.org
Subject: Re: A new, "org-bullets"-like minor mode
Date: Sun, 2 Feb 2020 21:00:54 +0100 [thread overview]
Message-ID: <02fe0132-09a8-d804-ff0b-344c08d625ee@posteo.net> (raw)
In-Reply-To: <87zhe0pz6i.fsf@bernoul.li>
> I haven't looked at the code yet but would it make sense for your new
> mode just being renamed to "org-bullet" instead? Do you expect that
> some current users won't want to update?
I have been considering that, but decided against replacing org-bullets
(or calling the package something akin to org-bullets+) for two reasons:
1) For the things I have/had in mind I would not have wanted to ensure
backwards-compatibility.
I would hate to see long-time users of org-bullets to experience
breakage because of design decisions I made. I think that there is a
lot of value in keeping a straightforward package with a singular goal
for people that want exactly that. While I made sure to ease the pain
of transitioning for people interested, I would not want to touch it
beyond maintenance. From what I know, spacemacs ships with it for
example, so I would not like to cause anything downstream without warning.
2) While there are perfectly valid reasons to name a package similar to
another ("xpackage", "packagex", "package+", "pakG", ...) I personally
shy away from the practice to avoid confusion. LaTeX packages are
notorious for this, and their overuse of this convention has led to many
frustrating afternoons for me in the past years.
> If you want to stick with creating a new mode, are there any bug fixes
> that you could backport to "org-bullet"?
I am sincerely considering to help maintain the project, to "adopt" it
from the orphanage, should org-superstar gain any popularity. I will
gladly port anything technical (bugfixes, plausible performance patches)
I can to org-bullets if requested, but I would not add features.
However, I hesitate to immediately pick up the role of maintaining
org-bullets for the simple reason that I'd first like to have a project
of my own to show for myself, as a proof of responsibility if you will.
> I don't actually use it myself and just enable it temporarily if someone
> reports a bug or something. It's not that I am not interested in
> something like this package, but from the sound of it I would rather use
> your package than the old "org-bullet".
If you find the time to check out my package, I am always open for
criticism and suggestions. Seeing how young the package is I am very
open to adding features and making quality of life improvements to the
interfaces.
> If I remember correctly it, then it took some effort to contact sabof,
> but eventually they gave their blessing.
I sent sabof a mail via the Github address, if you have any means of
communication with him, would you mind sharing them?
prev parent reply other threads:[~2020-02-02 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 15:49 A new, "org-bullets"-like minor mode D
2020-02-01 20:32 ` Marco Wahl
2020-02-01 20:47 ` D
2020-02-01 20:59 ` Marco Wahl
2020-02-01 21:19 ` Diego Zamboni
2020-02-01 22:57 ` org-superstar-mode: A re-imagining of org-bullets with new features D
2020-02-02 6:59 ` Bastien
2020-02-02 16:52 ` Adam Porter
2020-02-03 7:43 ` A new, "org-bullets"-like minor mode stardiviner
2020-02-04 10:43 ` D
2020-02-02 19:27 ` Jonas Bernoulli
2020-02-02 20:00 ` D [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02fe0132-09a8-d804-ff0b-344c08d625ee@posteo.net \
--to=d.williams@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jonas@bernoul.li \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).