talexander
/
organic
1
0
Fork 0
Code Issues Pull Requests Releases Activity
org-mode parser in rust
924 Commits 3 Branches 16 Tags 7.7 MiB
Rust 96.4%
Shell 1.8%
Dockerfile 0.9%
Makefile 0.8%
Go to file
Tom Alexander cc671925db
Support empty sections under headings. 		2023-08-29 16:07:43 -04:00
.lighthouse Update the run targets for the Makefiles for the docker containers. 2023-08-27 17:46:36 -04:00
docker Remove volumes in the clean step. 2023-08-27 17:53:51 -04:00
elisp_snippets Add all entities. 2023-08-29 15:16:22 -04:00
notes Put all trailing whitespace ownership test cases into the automated tests. 2023-08-20 16:03:31 -04:00
org_mode_samples Do not allow plain links without a path. 2023-08-29 15:44:04 -04:00
scripts Fix tracing in the run_docker_compare.bash script. 2023-08-28 01:18:45 -04:00
src Support empty sections under headings. 2023-08-29 16:07:43 -04:00
tests Add all entities. 2023-08-29 15:16:22 -04:00
.dockerignore Prefix the automatically generated tests. 2023-08-20 23:53:11 -04:00
.gitignore
…
Cargo.toml Add a script for testing organic parse times. 2023-08-27 16:56:32 -04:00
LICENSE
…
Makefile Fix make dockertest. 2023-08-27 22:41:55 -04:00
README.md Bump version to 0.1.2 and change README to markdown. 2023-08-11 00:00:49 -04:00
build.rs Only allow a single section under a heading. 2023-08-29 16:03:13 -04:00
rustfmt.toml
…

README.md

Organic - Free Range Org-Mode

Organic is an emacs-less implementation of an org-mode parser.

Project Status

This project is a personal learning project to grow my experience in rust. It is under development and at this time I would not recommend anyone use this code. The goal is to turn this into a project others can use, at which point more information will appear in this README.

License

This project is released under the public-domain-equivalent 0BSD license. This license puts no restrictions on the use of this code (you do not even have to include the copyright notice or license text when using it). HOWEVER, this project has a couple permissively licensed dependencies which do require their copyright notices and/or license texts to be included. I am not a lawyer and this is not legal advice but it is my layperson's understanding that if you distribute a binary with this library linked in, you will need to abide by their terms since their code will also be linked in your binary. I try to keep the dependencies to a minimum and the most restrictive dependency I will ever include is a permissively licensed one.