Re: Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?)

[Jonas Bernoulli]

Ihor Radchenko  writes:

> Jonas Bernoulli  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.

Re: Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?)

[Ihor Radchenko]

Jonas Bernoulli  writes:

>> 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.

That's fine to install htmlize. Org relies upon htmlize for certain
features, including HTML export.

However, we also recently added engrave-faces for LaTeX export. And
engrave-faces is advertised as successor to htmlize. So, we might
consider (in future) to offer engrave-faces as another option to export
HTML as well. (This idea has nothing to do with helping to maintain
htmlize - it will be relevant for a long time at least for users of
older Org versions, even if we decide to use engrave-faces instead of
htmlize).

>> 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.

Good point. Although all the pull requests appear to be rather trivial
from the first glance. Let's see if Hrvoje has anything to say.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?)

[Samuel Wales]

[fyi that is probably not related: i use htmlize.el for functions it
has that allow you to copy a region omitting invisible parts.  e.g.
partly folded magit.  i haven't found other code that workd for that
and myb rain could not construct any.]


On 8/13/23, Ihor Radchenko  wrote:
> Jonas Bernoulli  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.
>
> Note that Timothy wrote https://github.com/tecosaur/engrave-faces that
> provides similar functionality but not just for HTML.
>
> We might consider extending engrave-faces to cover all the htmlize
> features.
>
>> 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)
>
>> It seems to me it would be a good idea if Hrvoje gave one or more Org
>> maintainer commit access to this repository.  Alternatively we could
>> maintain it at https://github.com/emacsorphanage/htmlize, and I could
>> take care of giving commit access, but in that case Hrvoje would also
>> have to get involved briefly at least, to transfer the repository to
>> that organization.
>
> Also an option.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?)

[Ihor Radchenko]

Jonas Bernoulli  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.

Note that Timothy wrote https://github.com/tecosaur/engrave-faces that
provides similar functionality but not just for HTML.

We might consider extending engrave-faces to cover all the htmlize
features.

> 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)

> It seems to me it would be a good idea if Hrvoje gave one or more Org
> maintainer commit access to this repository.  Alternatively we could
> maintain it at https://github.com/emacsorphanage/htmlize, and I could
> take care of giving commit access, but in that case Hrvoje would also
> have to get involved briefly at least, to transfer the repository to
> that organization.

Also an option.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at