4 ms·
Re. parser: > organice has a custom parser for Org files. It works quite fine and has unit tests to prove it. One of the quality goals for the parser is that w
by WalterGR 4y ago
Re. parser:
> organice has a custom parser for Org files. It works quite fine and has unit tests to prove it. One of the quality goals for the parser is that when it parses and re-exports an Org file, it should not change the original file. Not seeing unrelated diffs is important for the productivity of the user. It sounds trivial, but lots of alternative products do not live up to this expectation.
- funcDropShadow 4y agoI've used that parser to write some custom tools for me, it chocked on one large file (30k lines) with lots of code blocks. It needed 30 min and dozens of GiB of RAM to parse that file, that was on the JVM not in the browser. But the next update of the parser combined with some strategic deletions of code blocks, made parsing fast enough.
- preek 4y agoI don't think you did. You probably used the sister project https://github.com/200ok-ch/org-parser https://github.com/200ok-ch/org-parser which has a well known issue regarding what you are describing: https://github.com/200ok-ch/org-parser/issues/56 https://github.com/200ok-ch/org-parser/issues/56 organice has no such performance issues (and does not run on the JVM). I use it daily with 5k LOC files.
- funcDropShadow 4y agoYou are right, I was under the assumption that Organice did use 200ok-ch/org-parser. Sorry, for the confusion.