summaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorbt <bt@web>2023-11-30 14:12:28 -0500
committerIkiWiki <ikiwiki.info>2023-11-30 14:12:28 -0500
commit79b98919f3976696a24349ae58a689ce4f1a2b68 (patch)
treeea68e2a7f12fbc41e89fc0fda567c7d9d978dd2c /posts
parent51aacaa1877794c5e679d3825013d2d00892acdc (diff)
Diffstat (limited to 'posts')
-rw-r--r--posts/sublime.md12
1 files changed, 4 insertions, 8 deletions
diff --git a/posts/sublime.md b/posts/sublime.md
index ddf70f3..2217c75 100644
--- a/posts/sublime.md
+++ b/posts/sublime.md
@@ -1,6 +1,5 @@
-# Launching Sublime Text with dmenu on Alpine Linux
-
-2023-04-13
+[[!meta title="Launching Sublime Text with dmenu on Alpine Linux"]]
+[[!meta date="2023-04-13"]]
Everyone seems to be running some version of VSCode as their main editor these days. But not me. I find VSCode to be too bloated for my needs - not to mention being built on top of electron instead of *native* code. I prefer running programs that don't try to devour all of my machine's available memory or spike my CPU.
@@ -10,7 +9,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 +47,5 @@ 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.