From 491f79d34da2b261c4ea4fa26565ecc38627d6ce Mon Sep 17 00:00:00 2001
From: Ewout Wieten <ewout@ewy.one>
Date: Tue, 10 Jan 2023 14:50:12 +0100
Subject: Add headers to cmd post

---
 entry/cmd/index.html | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'entry/cmd')

diff --git a/entry/cmd/index.html b/entry/cmd/index.html
index 769f87d..c2cc005 100644
--- a/entry/cmd/index.html
+++ b/entry/cmd/index.html
@@ -28,6 +28,7 @@
         doing serious development work. Not the least of which: running any kind of script pops up this annoying, ugly
         black box, cmd.exe: the glue between MS-DOS and Windows 95.
     </p>
+    <h2>Shells and terminals</h2>
     <p>
         On non-toy operating systems, there is a distinction between the shell and the terminal: a shell is used to
         interface with programs and the kernel, while the terminal is used to display the in- and output streams from
@@ -35,6 +36,7 @@
         the execution and the in- and output. This also means when a program executes an external script, it will give
         you a pretty little command prompt.
     </p>
+    <h2>Bandages</h2>
     <p>
         Of course, there are situations where you would not want a popup to appear. If you are running startup scripts,
         then you will probably be annoyed by the black boxes which appear on boot every time. Sometimes they don't
@@ -52,6 +54,7 @@
             from showing up. Then, close the window from the first script, and the second script will continue running!
         </li>
     </ul>
+    <h2>Painkillers</h2>
     <p>
         The only actual solution I've found acceptable over the years was a little tool which, if I remember correctly,
         was called "run.exe" and produced by the same people behind XMing, the Windows X server implementation, which
-- 
cgit v1.3