New post: Seven Spanish verbs to make your future-wife cry with

cli.html

@@ -18,7 +18,8 @@
 			<ul>
 				<li><b>nmtui</b>: Wi-Fi manager for those of us who haven't been forcibly upgraded to Connman. Arrow keys navigate. Connecting to a new network is as simple as going to "Activate a connection", pressing enter on the network wanted, and then typing in the password... provided that your network is a simple WPA/WPA2 one like a residential home router, and isn't doing some fucky credentials/certificate thing like a corporate network.</li>
 				<li><b>pandoc</b>: (almost) universal document converter. I write my posts in Markdown and then use Pandoc to convert them to HTML... albeit a huge chunk of HTML with no line breaks between the paragraphs. It will insist on using non-ASCII characters in otherwise-ASCII file formats unless you beat it over the head with the command-line flags <code>--ascii --wrap=none</code>, but even then it'll just use the <a href="https://www.rapidtables.com/web/html/html-codes.html">character code</a> instead.</li>
-				<li><b>elinks</b>: a browser for the terminal... not to be confused with <code>links</code> or <code>lynx</code>. I used to use <code>lynx</code> because of the Gopher support that <code>elinks</code> lacks, but I've never been able to successfully compile <code>lynx</code> with TLS support. <code>elinks</code>, on the other hand, compiles in a snap with no problems. It also has slightly better text formatting and keyboard shortcuts. (The H key pops up the browsing history, for example, and G asks you which URL you want to go to next.) My only complaint is that it won't let me select text to copy to the clipboard with my mouse.</li>
+				<li><b><a href="https://github.com/gottox/smu">smu</a></b>: another document converter, but it only goes from a subset of Markdown to HTML. It compiles in under a second on my computer and doesn't require a kajillion Haskell dependencies like <code>pandoc</code> does.</li>
+				<li><b>elinks</b>: a browser for the terminal... not to be confused with <code>links</code> or <code>lynx</code>. I used to use <code>lynx</code> because of the Gopher support that <code>elinks</code> lacks, but I've never been able to successfully compile <code>lynx</code> with TLS support. <code>elinks</code>, on the other hand, compiles in a snap with no problems. It also has slightly better text formatting and keyboard shortcuts. (The H key pops up the browsing history, for example, and G asks you which URL you want to go to next.) My only complaint is that it won't let me select text to copy to the clipboard with my mouse without an arcane keyboard combination I've already forgotten.</li>
 				<li><b>cvlc</b>: VLC, but in the terminal! I <a href="./tutorials/vlc.html">wrote a tutorial</a> about using it a while ago. You almost certainly want to use the ncurses frontend.</li>
 				<li><b>byobu</b>: terminal multiplexer, which is a fancy way of saying "please let me run more than one program at a time in a TTY". Basically <code>tmux</code> but better, although it can use GNU <code>screen</code> as a backend too. Comes with a fancy little status bar at the bottom of the screen that displays info about your system, such as system load, disk usage, and battery status (which is a godsend when using a TTY on a laptop). The info it displays can be changed by pressing F1 or running <code>byobu-config</code>.</li>
 				<li><b>tree</b>: recursively lists all the files in a given folder... and every folder in there... and every folder in those folders... hence the <i>recursive</i>. If you've lost a file but know part of its name, you can run <code>tree -f | grep "SearchTerm"</code> to find it. (If you're searching by content, just use <code>grep -nr "SearchTerm"</code> instead.)</li>