You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be handy to automate the export process of all org-files to html, after all literate programming would like to be more readable with html from time to time
It would be even better to have all of them to be in one html file, or make them accessible without any manual intervention.
Any readable alternative would be fine.
Thanks!
The text was updated successfully, but these errors were encountered:
I've toyed with this in the past (hence also the setup.org file), but a multifile export requires some Elisp setup procedure/magic and I never managed to get expected/usable results. Maybe you can help w/ that?
Also, in the meantime (and largely thanks to @wallyqs efforts) GH has become a decent platform to publish org files. Examples:
But I'd still love to also be able to publish a whole org project to other formats, e.g. in order to generate ebooks, so any help would be highly appreciated
I've toyed with this in the past (hence also the setup.org file), but a
multifile export requires some Elisp setup procedure/magic and I never
managed to get expected/usable results. Maybe you can help w/ that?
Also, in the meantime (and largely thanks to @wallyqs https://github.com/wallyqs efforts) GH has become a decent platform to
publish org files. Examples:
But I'd still love to also be able to publish a whole org project to other
formats, e.g. in order to generate ebooks, so any help would be highly
appreciated
—
Reply to this email directly or view it on GitHub #5 (comment).
It would be handy to automate the export process of all org-files to html, after all literate programming would like to be more readable with html from time to time
It would be even better to have all of them to be in one html file, or make them accessible without any manual intervention.
Any readable alternative would be fine.
Thanks!
The text was updated successfully, but these errors were encountered: