From 2a3b2e7737a50c87dd154e0f2fa48905055f58b0 Mon Sep 17 00:00:00 2001
From: bth <git@bth.moi>
Date: Sun, 14 Jan 2024 12:03:38 -0800
Subject: [PATCH] readme

---
 README.md | 21 ++++++++++++++++++---
 1 file changed, 18 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index f74aa9d..df7285a 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ It consists of two parts:
 
 1. Elisp for functionality within emacs. Most of it is integrated directly with the `project` interface, and consists the ability to find a file from a filename.
 
-2. Bash scripts for the commandline interface. I prefer a CLI for file creation and management rather than more emacs functions, because chaining shell commands is easy and I think of the commandline as the point of reference for all filesystem management.
+2. Shell scripts for the commandline interface. I prefer a CLI for file creation and management rather than more emacs functions, because chaining shell commands is easy and I think of the commandline as the point of reference for all filesystem management.
 
 Conceptually, `um` is somewhat like org-roam, except without any database dependency. (And it assumes Markdown rather than org, which I don't care for.)
 
@@ -22,7 +22,22 @@ The "database" depends on a few simple ideas:
 
 4. Using the built-in emacs `project` package to organize compositions built from these source files.
 
-## config
+## installation
+
+Clone it:
+
+```
+git clone https://git.bth.moi/bth/um.git ~/um
+```
+
+Symlink the `um` CLI somewhere in your `PATH`:
+
+```
+cd ~/um
+ln -s ~/um/shell/um /usr/local/bin/um
+```
+
+## emacs config
 
 My config looks like this:
 
@@ -35,6 +50,6 @@ My config looks like this:
 
   (advice-add 'embark-target-file-at-point :around 'uldb-file-at-point-advice)
 
-  :load-path "~/dev/um/elisp"
+  :load-path "~/um/elisp"
 )
 ```