New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any plans to adapt to the new Org export framework #19

Closed
tarsius opened this Issue Jan 6, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@tarsius
Copy link

tarsius commented Jan 6, 2017

org-html.el is no longer part of Org, as the old export framework that it was part of has been removed. Do you intend to adapt this for the new export framework in recent Org versions?

@mattfidler

This comment has been minimized.

Copy link
Owner

mattfidler commented Jan 12, 2017

I have stopped using this, so I'm likely not going to adapt the more recent framework. @vapniks may still use it and adapt it.

@tarsius

This comment has been minimized.

Copy link

tarsius commented Jan 12, 2017

Alright. I will wait a little for @vapniks, and if he doesn't state that he's going to adapt this, then I will remove it from Melpa and move it from the Emacsmirror to the Emacsattic.

@mattfidler

This comment has been minimized.

Copy link
Owner

mattfidler commented Jan 12, 2017

Do you know if anyone downloaded it recently. I saw over 1000 downloads on melpa. It may be more popular than I anticipated...?

@tarsius

This comment has been minimized.

Copy link

tarsius commented Jan 12, 2017

Unfortunately it's not possible to know when those downloads were made. There's an issue about that on the Melpa issue tracker: melpa/melpa#4376. Also relevant is the other issue mentioned there (melpa/melpa#4384).

So the idea is that we remove it, and if someone complains then it can be added back.

/cc @purcell

@vapniks

This comment has been minimized.

Copy link
Collaborator

vapniks commented Jan 21, 2017

org-html is not required, it's optional. So I'm not sure it needs to be adapted. I haven't tested it fully, but it seems to be working.

@tarsius

This comment has been minimized.

Copy link

tarsius commented Jan 22, 2017

I just took a closer look, and it indeed seems that org-html is only required for backward compatibility. If that feature is not available, then (org-export-replace-region-by 'html) is used instead of org-replace-region-by-html.

@tarsius tarsius closed this Jan 22, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment