From: Ihor Radchenko <yantar92@posteo.net>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien Guerry <bzg@gnu.org>, Maske <maske1foro@gmail.com>,
Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Should we move constants.el by Carsten Dominik to Org orphanage?
Date: Sun, 04 Aug 2024 17:43:20 +0000 [thread overview]
Message-ID: <87ttg0dw07.fsf@localhost> (raw)
In-Reply-To: <CADn3Z2LgaV8VTA7-zUq+0215NAaYNKgJ1zVmjHxrn4MiM58w+Q@mail.gmail.com>
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Mon, Oct 16, 2023 at 12:12 PM Bastien Guerry <bzg@gnu.org> wrote:
>
>> Ihor Radchenko <yantar92@posteo.net> writes:
>>
>> > Bastien Guerry <bzg@gnu.org> writes:
>> >
>> >> I see no reason not to use
>> >> https://github.com/cdominik/constants-for-Emacs as the source for
>> >> constants.el, the package seems stable (as its name suggests...)
>>
>
> Yes, this is stable, and I am still maintaining it.
Thanks for chiming in :)
Have you considered publishing constants.el as GNU/non-GNU ELPA package?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-08-04 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 12:02 Erratum in "The Org Manual" 9.6 Maske
2023-09-11 8:13 ` Ihor Radchenko
2023-09-11 8:18 ` Should we move constants.el by Carsten Dominik to Org orphanage? (was: Erratum in "The Org Manual" 9.6) Ihor Radchenko
2023-10-16 5:46 ` Should we move constants.el by Carsten Dominik to Org orphanage? Bastien Guerry
2023-10-16 9:11 ` Ihor Radchenko
2023-10-16 10:11 ` Bastien Guerry
2024-08-04 9:05 ` Carsten Dominik
2024-08-04 17:43 ` Ihor Radchenko [this message]
2024-08-04 18:41 ` Carsten Dominik
2024-08-04 18:51 ` Ihor Radchenko
2024-08-04 20:24 ` Colin Baxter
2024-08-07 4:56 ` Carsten Dominik
2024-08-08 7:45 ` Ihor Radchenko
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=87ttg0dw07.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maske1foro@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.