Home

Docs for OrgExtended are located in their own repo.

Here I would like to talk about where I am thinking to take the plugin in the hopes of sparking conversation.

One of my personal beefs with my sublime plugin is that when I open multiple copies of sublime, I tend to have multiple copies of my org files in memory. This really isn't a huge deal but it feels wasteful to me. For a while now I have had a desire to offload a lot of the org functionality out of the sublime plugin itself into a reusable service. To that end I have been working on an org service (written in go) with the intention of allowing the org mode plugin to work off that plugin eventually rather than off its own parsing of org files, kind of like LSP, but for org files.

This will buy me a couple of things.

1. Make it easier to support org more effectively in other editors. If I wanted to improve vscode or vim, or... clion with orgmode support, I could.
2. Provide me with web based access to my orgmode files. I am working on a little portal.
3. Will provide access to more libraries. Sublime plugins have limited access to pip, anything I want to import I have to pull into the plugin itself, which is frustrating and makes the plugin pretty bloated.
4. If I am working at the command line I don't have to fire up sublime to answer a quick question about my tasks.

I am currently working on a websocket based server for parsing and managing org files. I have a command line tool and a web portal I am hacking on to prove that this is generic enough for my needs.