8000 migrating from orgize · Issue #18 · org-rs/org-rs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

migrating from orgize #18

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.

Sign up for GitHub

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

Jump to bottom
Open
PoiScript opened this issue Apr 16, 2019 · 2 comments
Open

migrating from orgize #18

PoiScript opened this issue Apr 16, 2019 · 2 comments

Comments

@PoiScript
Copy link

Hello, org-rs contributors! I'm the author of orgize, yet another org-mode parser written in Rust. I had been working on that project for a few months. I'm glad to know that we are sharing the same goal.

Consider that org-rs is more organized and get more attention. I would like to share my work to the community by migrating orgize to org-rs. orgize is a hand-written parser, so it should be pretty easy for migrating.
@scotttrinh
Copy link
Contributor

Hey @PoiScript ! It's so great to see so many people who have written or started writing org parsers at roughly the same time all over the world!

What do you suppose is your idea of integrating into the existing org-rs structure? I think where we're at currently is that org-rs/org-rs is a working implementation of the elisp parser ported to Rust. My own project was an attempt at something more rusty, but is far from usable, and your own hand-rolled parser seems yet another take with some additional functionality.

It would be good for the community, I think, if there was a coherent reason for the org to exist and have the relationship between the different projects well-understood. Perhaps if we have some time over the next week to chat we can have a high-level idea of where we go from here? Care to join us over on our Gitter? https://gitter.im/org-rs/community

@PoiScript
Copy link
Author

Thank you for your quick response.

What do you suppose is your idea of integrating into the existing org-rs structure?

Yes, like I said before, I had been working on an implementation for a few months. It can handle almost everything now except for tables and some complicated elements (like inlinetasks).

So I think it's a good way for both of us to work together and push forward the progress instead of working separately.

For the parser design, my project is heavily inspired by the well-known pulldown-cmark which you might want to have a look. Also, if I get it right, the elisp parser is rely on regex which we should take it into consideration.

I had join the Gitter chat room and am excited to further discuss about implementation there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scotttrinh @PoiScript
0