All of ekg’s data is stored in a sqlite database. Notes are organized around tags, and you can view many notes by looking at one or more tags.

Editing a note from one of these buffers, or capturing a new note, lets you edit both the note’s text content and its metadata (mostly tags you add to it) in a separate buffer.

ekg has functionality to have notes created with templates that vary based on the tags you are using. It also supports saving unfinished notes as drafts.

Notes can be on file resources and web resources. You can use notes on file resources to have a stored annotation for files.

ekg supports import from org-roam, and import and export to logseq. It also supports inline commands, which can be used for transclusion and any other functionality you may need.

There is support for attaching Large Language Model (LLM) “embeddings” to notes, for use in search and similarity search, via the llm package. This allows you to search based on semantics, as opposed to text matching. You can also use LLM chat in your notes, getting an LLM to respond to your notes based on a default prompt, or new prompts that you add.

Additionally, a video demonstration and explanation of ekg is on YouTube. This README has only the most basic information, but the full information can be found in the manual, which can be viewed in the Emacs info after installing.

There are a few core ideas driving the design of ekg. The first is that a title and a tag are the same thing. This isn’t unique to ekg: other tools such as Logseq also consider tags to be equivalent to pages of the same name, although in Logseq this functionality is limited since tags can only be single words. In org-roam, a tag is just a tag, so you can have a note called “emacs” and a tag called “emacs”, but these are not related. ekg takes the idea a step further: there are (mostly) no titles, only tags. So, instead of writing text in a note called “emacs”, just write a note and tag it with “emacs”. There is no “title”, only tags. If you write another note about emacs, also tag it “emacs”, and maybe something else too. Or tag it something more involved, like an idea: “emacs’s power derives from putting all data in buffers, and making all commands deal with buffers.” That’s a perfectly fine tag, and if you notice a connecting idea, you can tag it with this as well.

The advantage of this method is that it solves something that has bothered me for a while about the recent suite of tools like org-roam: backlinks are non-symmetrical. If you enter a note in your org-roam daily about emacs, and link it to the emacs note, then when you go to the emacs note, you have to explicitly enable the backlinks buffer to see the daily entry where you first entered it. Systems such as Logseq and the original Roam have backlinks alongside normal content, but this doesn’t seem possible in emacs, where a buffer of a file is expected show the file, and tricks with overlays can’t solve the issue. Even if it could, I want a system in which it doesn’t matter where you enter the data, it shows up in the original place the same as everywhere else it is linked to, not as a backlink, but just as part of the content. Having notes with no title, only tags, makes this possible, because there is no longer a difference between linking and writing the context, both are denoted by tags.

As a consequence of this design, notes can be small, because to add another note to a subject, you don’t need to append to an existing note, you can create another note.

Additionally, ekg has another key difference: it uses sqlite instead of the filesystem. When notes are small and do not have titles, files don’t make a lot of sense anymore. Additionally, the filesystem is limited. Even in org-roam, which uses it, it needs to be augmented with sqlite anyway to enable fast querying of tags and other operations. The sqlite-only approach also means it is much easier to make certain kinds of changes, since they only involve changing the database and not the text as well. In general, text and data are separated as much as possible here, so there’s no need or desire for the text to have to store data as well, we leave that completely to the database.

Another concept, loosely applied in ekg, is that of tags with standard prefixes. By default, date tags are prefixed with “date/”. This is a way to distinguish date tags from other kinds of tags. Most tags shouldn’t need it, but it often is useful to have prefixes to group tags in some way. For instance, perhaps all idea tags should be prefixed with “idea/”. In my ekg repository I use in my company, I have “person/” as a tag prefix for my coworker’s username.

The benefit of this is that it’s now possible to narrow in on just tags of a certain type if necessary.

There are a few other types of prefixes commonly used for tags. One is that titled resources have default tags that are prefixed with “doc/”, followed by the name of the document.

Functionality such as templates and LLM prompting can work with prefixed tags, so when looking for templates or prompts for a tag with some hierarchy, ekg will look at the tag hierarchy from the top to the bottom to add any relevant information.

ekg is currently hosted on MELPA. It requires Emacs 28.1 or higher and the the following packages:

• triples, which is a way to express a graph in sqlite in emacs, alongside basic querying functionality.
• llm, a way to depend on LLMs via an interface, so the user can choose which provider they want to use.

Emacs versions prior to version 29 are dependent on emacsql to provide sqlite functionality, which itself has a dependency on having a sqlite binary available on your system.

An example installation using use-package is below:

(use-package ekg
  :bind (([f11] . ekg-capture)))

If you are using embedding and llm functionality, an example in which you use Open AI’s API is the following:

(use-package ekg
  :bind (([f11] . ekg-capture))
  :init
  (require 'ekg-embedding)
  (ekg-embedding-generate-on-save)
  (require 'ekg-llm)
  (require 'llm-openai)  ;; The specific provider you are using must be loaded.
  (let ((my-provider (make-llm-openai :key "my-openai-api-key")))
    (setq ekg-llm-provider my-provider
          ekg-embedding-provider my-provider)))

Note: make sure to never check in an API key, so if you check in your configuration, set up your API key in a loaded elisp file you do not check in.

To create a note, run ekg-capture to capture a text note, or ekg-capture-url to capture a website. The note will, by default, be tagged with the current date. This can be changed by changing the variable ekg-capture-auto-tag-funcs, which is a series of functions that are called and can add tags.

At the top of the note is a special section, which will be unfamiliar. This is the metadata section, where it stores and displays editable metadata, notably tags, but possibly other data such as URLs. If you want to change tags, just edit them in the metadata section. Tags will autocomplete based on the tags you’ve already created.

The basic read operation in ekg is to show a list of notes according to some rule. An example is ekg-show-notes-with-tag. The notes displayed can be navigated between using n and p, and interacted with. The following section has a complete list of commands and keybindings.

Global commands, can be run everywhere, and most should be bound to useful keybindings:

These are also global commands, but for more occasional or specialized uses:

Commands relevant to capture buffers:

Commands relevant to edit buffers:

Commands relevant to note view buffers: