aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-07-02 14:47:32 -0400
committerBradley Taunt <bt@btxx.org>2024-07-02 14:47:32 -0400
commit62874c637e698af29be6206fb38dae46710b2e8c (patch)
treeb1daf2d4a5b084502849fca3c4ea54b195a44385
parente57e20a503cb94615527b9fceeb2fa7cbe8d4ac9 (diff)
Testing out footnotes with lowdown
-rw-r--r--posts/sublime.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/posts/sublime.md b/posts/sublime.md
index ddf70f3..2cfedd4 100644
--- a/posts/sublime.md
+++ b/posts/sublime.md
@@ -10,7 +10,7 @@ In case the title of this post didn't make this obvious, my editor of choice is
The only minor downside is that it isn't *fully* open source. Personally, I think it is well worth buying a license directly from the developers to support their efforts.
-If you haven't played around with it yet, I highly recommend giving it a try. At the very least, I guarantee you'll be impressed with the editor's performance and speed! [<#1>]
+If you haven't played around with it yet, I highly recommend giving it a try. At the very least, I guarantee you'll be impressed with the editor's performance and speed! [^1]
## One Small Problem...
@@ -48,8 +48,4 @@ doas ln -s ~/.local/share/flatpak/exports/bin/com.sublimetext.three /usr/bin/sub
Now that those directories are linked, simply open dmenu and start typing `sublimetext`. Done and done. No more terminal commands needed to open Sublime!
-- - -
-
-<small>
-1. <span id="1">I am aware that using a terminal-based editor such as vim or emacs would be even *more* efficient. For my own personal use I find more classical "IDE" applications to work best for me.</span>
-</small> \ No newline at end of file
+[^1]: I am aware that using a terminal-based editor such as vim or emacs would be even *more* efficient. For my own personal use I find more classical "IDE" applications to work best for me. \ No newline at end of file