Hey! Yes, I have started working on one in July. I have also been working on documentation for org-export, because right now it simply doesn't exist. No, reading org-element code is not documentation, and it's not even "self-documentation", because I had to read the code itself and not the automatically generated documentation that appears when I use `C-h f`, since the actual docstrings are templated garbage. So yeah, but I don't think I'll be finishing it any time soon. I may upload it to github if you need it though.
this post was submitted on 08 Oct 2023
3 points (100.0% liked)
Emacs
337 readers
1 users here now
A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!
Get Emacs
Rules
- Posts should be emacs related
- Be kind please
- Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.
Emacs Resources
Emacs Tutorials
- Beginner’s Guide to Emacs
- Absolute Beginner's Guide to Emacs
- How to Learn Emacs: A Hand-drawn One-pager for Beginners
Useful Emacs configuration files and distributions
Quick pain-saver tip
founded 2 years ago
MODERATORS
I may upload it to github if you need it though
Please do.
I did upload it, but it was deleted for some reason. on github: filipencopav/unfinished-ox-typst
Thanks.
For reference https://github.com/typst/typst
Looking quickly at the spec, I don't think much of the typst functionality would be used by an org exporter.
If you are interested in such an exporter, I'd recommend you put together a description of the mappings that you'd like to see. That is, what org features do you need and how does that translate into a typst feature; I'm not asking for an implementation, just guidance on the scope of a first-pass at the exporter. That will give someone with the technical skills to implement an org exporter guidance as to what features to focus on.