From: Jay Kamat <jaygkamat@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: rmsbolt.el [Was: Colorful line numbers]
Date: Sat, 23 Jul 2022 07:53:37 -0700 [thread overview]
Message-ID: <87tu77vq1a.fsf@eve> (raw)
In-Reply-To: <CALDnm50Ob0zQoxDN9bREGHwxYb6n_k7HEObq+FaXdiSGGoAQzg@mail.gmail.com>
João Távora writes:
> Changing the subject completely, I wonder if there's any interest in
> adding rmsbolt.el to GNU Elpa or even to core. It's not just for C/C++,
> it works for a bunch of languages.
I am personally open to putting the package on ELPA (or nongnu ELPA). My main
concern is that I would prefer to keep upstream where it is to avoid moving
things around - and ideally I would like to avoid doing extra work for new
versions (melpa automatically builds new versions every time I push/tag a
release). I haven't followed elpa very closely but my impression is that you
might be able to set a remote upstream but you would need to manually keep
re-syncing to keep things up to date in elpa.
Somewhat related, I think a better candidate for ELPA right now is the
org-notify package, which was dropped from org-contrib a while ago:
-
https://git.sr.ht/~bzg/org-contrib/commit/c6aef31ccfc7c4418c3b51e98f7c3bd8e255f5e6
- https://github.com/melpa/melpa/pull/8116
I'm not the maintainer of this package, but I would like to see this package
published on ELPA, nongnu ELPA, or Melpa. Depending on what the maintainer
prefers, I would be happy to put in any work required to get the package back
on ELPA (either in org-contrib or on its own).
> Apologies if it's old news and everyone's been using this, but
> it's the best package I've seen appear in some time.
Thanks for the kind words :). I wish I had more time to work on it but I've
been quite busy in recent years unfortunately.
-Jay
next prev parent reply other threads:[~2022-07-23 14:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:50 Colorful line numbers João Távora
2022-07-22 11:00 ` Eli Zaretskii
2022-07-22 11:29 ` João Távora
2022-07-22 11:42 ` Eli Zaretskii
2022-07-22 12:02 ` João Távora
2022-07-22 13:27 ` Eli Zaretskii
2022-07-22 13:53 ` João Távora
2022-07-22 14:33 ` Eli Zaretskii
2022-07-22 15:10 ` João Távora
2022-07-22 15:38 ` Eli Zaretskii
2022-07-22 16:30 ` rmsbolt.el [Was: Colorful line numbers] João Távora
2022-07-22 19:53 ` Stefan Monnier
2022-07-23 6:13 ` Eli Zaretskii
2022-07-23 9:35 ` João Távora
2022-07-23 10:25 ` Eli Zaretskii
2022-07-23 14:43 ` Stefan Monnier
2022-07-23 15:52 ` Eli Zaretskii
2022-07-23 16:31 ` Stefan Monnier
2022-07-23 17:07 ` Colorful line numbers Eli Zaretskii
2022-07-23 18:18 ` rmsbolt.el [Was: Colorful line numbers] João Távora
2022-07-23 18:11 ` João Távora
2022-07-23 14:53 ` Jay Kamat [this message]
2022-07-23 17:25 ` Stefan Monnier
2022-07-23 17:34 ` Eglot to core [Was: rmsbolt.el [Was: Colorful line numbers]] João Távora
2022-07-23 17:52 ` Stefan Monnier
2022-07-24 18:58 ` João Távora
2022-07-24 19:04 ` Stefan Monnier
2022-07-25 1:05 ` Po Lu
2022-07-25 2:45 ` Stefan Monnier
2022-07-25 5:55 ` Philip Kaludercic
2022-07-25 15:31 ` Stefan Monnier
2022-07-25 6:23 ` Po Lu
2022-07-25 10:49 ` Bozhidar Batsov
2022-07-25 11:01 ` João Távora
2022-07-25 11:50 ` Felician Nemeth
2022-07-25 12:27 ` João Távora
2022-07-25 12:29 ` João Távora
2022-07-25 15:00 ` Felician Nemeth
2022-07-25 15:41 ` João Távora
2022-07-26 8:12 ` Felician Nemeth
2022-07-26 8:21 ` João Távora
2022-07-26 8:55 ` Felician Nemeth
2022-07-25 16:07 ` Max Brieiev
2022-07-25 17:05 ` João Távora
2022-07-25 15:33 ` Stefan Monnier
2022-07-22 12:18 ` Colorful line numbers Dmitry Gutov
2022-07-22 12:38 ` Stefan Monnier
2022-07-22 13:41 ` Dmitry Gutov
2022-07-22 14:01 ` João Távora
2022-07-22 23:32 ` Stefan Monnier
2022-07-23 18:50 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu77vq1a.fsf@eve \
--to=jaygkamat@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.