From: Jonas Bernoulli <jonas@bernoul.li>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Bastien Guerry <bzg@gnu.org>, Greg Minshall <minshall@umich.edu>,
emacs-orgmode@gnu.org, flexibeast@gmail.com, hniksic@gmail.com,
Timothy <orgmode@tec.tecosaur.net>
Subject: Re: Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?)
Date: Mon, 14 Aug 2023 15:15:38 +0200 [thread overview]
Message-ID: <87zg2t9345.fsf@bernoul.li> (raw)
In-Reply-To: <87wmxzdkdt.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Jonas Bernoulli <jonas@bernoul.li> writes:
>
>> `htmlize' is currently maintained at https://github.com/hniksic/emacs-htmlize
>> but its maintainer hasn't been responding to any issues and pull-requests
>> for quite some time now and seems to be inactive on Github altogether.
>
> Hmm... Org has built-in htmlize support and I did not know that it is
> not maintained actively.
I only installed htmlize because org-html-fontify-code told me to do so.
Should it not have done that? I did not have any version of htmlize
installed prior to this.
>> Regardless of where this package will eventually end up being
>> maintained, it would be a good idea to keep it on Github at least until
>> most of the issues and pull-requests that have already been opened there
>> have been resolved.
>
> Or we can simply hand-pick that 13 open Github issues and transfer them
> manually. (Does not mean that we have to do it, but I see not why having
> a few issues on Github should be a blocker to anything)
The idea was to let those who have already opened pull-requests on
Github and have been patiently waiting for a response ever since, to
finish the work there.
next prev parent reply other threads:[~2023-08-16 12:39 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:17 [MAINTENANCE] Org orphanage? Ihor Radchenko
2022-11-21 11:02 ` Bastien
2022-11-21 11:53 ` Ihor Radchenko
2022-11-22 0:45 ` Alexis
2022-12-11 10:29 ` Ihor Radchenko
2022-12-29 16:13 ` Bastien
2022-12-31 12:31 ` Ihor Radchenko
2023-01-02 15:07 ` Bastien
2023-01-02 15:12 ` Ihor Radchenko
2023-01-02 15:28 ` Bastien
2023-01-03 10:45 ` Ihor Radchenko
2023-01-04 9:30 ` Bastien
2023-01-05 11:02 ` Ihor Radchenko
2023-01-05 11:30 ` Bastien
2023-01-06 1:54 ` Samuel Wales
2023-01-06 8:09 ` Greg Minshall
2023-01-06 8:23 ` Bastien Guerry
2023-01-06 16:51 ` Ihor Radchenko
2023-01-06 17:06 ` tomas
2023-01-07 10:07 ` Bastien
2023-01-07 10:19 ` Bastien Guerry
2023-02-04 13:57 ` Ihor Radchenko
2023-08-16 15:33 ` Jonas Bernoulli
2023-08-17 12:28 ` Ihor Radchenko
2023-07-31 11:13 ` Ihor Radchenko
2023-08-13 15:11 ` Jonas Bernoulli
2023-08-13 15:36 ` Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?) Ihor Radchenko
2023-08-14 1:30 ` Samuel Wales
2023-08-14 13:15 ` Jonas Bernoulli [this message]
2023-08-14 13:35 ` Ihor Radchenko
2023-08-14 16:17 ` Htmlize support, maintenance, and Org mode Bastien Guerry
2023-08-14 16:22 ` Ihor Radchenko
2023-08-14 16:30 ` Bastien Guerry
2023-08-15 10:21 ` Timothy
2023-08-14 13:58 ` Philip Kaludercic
2023-08-14 14:14 ` Ihor Radchenko
2023-08-14 14:18 ` Philip Kaludercic
2023-08-14 14:32 ` Ihor Radchenko
2023-08-14 16:20 ` Bastien Guerry
2023-08-14 16:24 ` Ihor Radchenko
2023-08-15 10:27 ` [MAINTENANCE] Org orphanage? Hrvoje Nikšić
2023-08-15 16:12 ` Ihor Radchenko
2023-08-20 20:41 ` Hrvoje Nikšić
2023-08-16 15:16 ` Jonas Bernoulli
2023-08-17 12:27 ` Ihor Radchenko
2023-08-17 13:41 ` Jonas Bernoulli
2023-08-17 15:08 ` Corwin Brust
2023-08-21 7:46 ` Ihor Radchenko
2023-08-24 18:22 ` Jonas Bernoulli
2023-08-25 10:07 ` Ihor Radchenko
2023-08-18 9:19 ` Ihor Radchenko
2023-08-18 13:32 ` Alexis
2023-08-22 15:13 ` Bastien Guerry
2023-08-24 17:49 ` Jonas Bernoulli
2023-08-24 18:24 ` Bastien Guerry
2022-11-21 22:19 ` Tim Cross
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=87zg2t9345.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@gmail.com \
--cc=hniksic@gmail.com \
--cc=minshall@umich.edu \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@posteo.net \
/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).