From: "Dwarshuis\, Nathan J" <firstname.lastname@example.org>
To: Emacs Org Mode mailing list <email@example.com>
Subject: org-mode functional programming library
Date: Mon, 20 Jan 2020 18:47:52 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
I recently authored an package called "om.el" which is a functional org-mode API akin to dash.el primarily using org-element. Briefly, it provides a library of (mostly) pure functions that manipulate the parse tree generated by org-element.el, and uses this to either edit or query the buffer with all the advantages of functional programming (eg lack of side effects, referential transparency, easier testing, etc). The github repo for om.el is here: https://github.com/ndwarshuis/om.el.
I'm posting to the mailing list a) for general feedback on this package and b) because I am wondering if this would be a good package to include with org-mode itself rather than in another repository such as MELPA. The code for om.el is tightly integrated with org-element.el and it might make sense for development between these to be closely intertwined.
There is also an open submission for this to MELPA and the discussion is here: https://github.com/melpa/melpa/pull/6623.
next reply other threads:[~2020-01-20 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 23:47 Dwarshuis, Nathan J [this message]
2020-01-21 15:23 ` org-mode functional programming library Tim Visher
2020-02-01 13:53 ` Nicolas Goaziou
2020-02-04 4:29 ` Dwarshuis, Nathan J
2020-02-04 7:43 ` Adam Porter
2020-02-11 8:13 ` Bastien
2020-02-12 16:07 ` Dwarshuis, Nathan J
2020-02-12 17:35 ` Bastien
2020-07-24 16:07 ` Dwarshuis, Nathan J
2020-07-27 13:55 ` Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).