Slowing turning Obsidian into emacs: Init file and commands

@readwithai (𝕏)

I intend to implement some AI, PDF and productivity code in Obsidian. As part of this process I am moving over from emacs org-mode to Obsidian and also developing other plugins that I find useful as I go.

One of these plugins is REPL . This is designed to emulate some of the features of emacs that allows you to easily and quickly prototype code to automate emacs from within emacs itself. This is both useful for “on off” tasks and for developing code that might be turned into plugins.

I’m quite happy with some of the features I have created so far, although this will never be emacs for a few reasons: javascript seem to lack the introspection necessary to add documentation to methods that can easily be accessed, when dynamically executing code in obsidian it is natural to use javascript but most plugins are written in typescript, the “data modely” or obsidian isn’t as complete as emacs with it’s overlays - rather code can add html.

I have just added a couple of cool features. The ability to define new command programmatically and the ability to use an “init file” analogous to `init.el` or `vimrc` which runs add startup. This makes it easy to quickly hack up easy features and then define short cuts for them.

Here’s a video demoing the feature.

I plan to continue working on features for Obsidian. I am currently working on some features to highlight PDFs based on AI search and plan to working a time clocking app. If this sounds interesting you might like to follow me on 𝕏 or subscribe here. I also write on philosophical topics related to reading and the information ecosystem.

---