commit a6d34e53b2d161b68972f1cd52fae14ef904cae8
Author: Simon Watson <spw01@protonmail.com>
Date: Fri Jan 21 15:52:06 2022 -0500
Updates
diff --git a/2022-01-20-gopher-setup.org b/2022-01-20-gopher-setup.org
index 532ae59..1a6205f 100644
--- a/2022-01-20-gopher-setup.org
+++ b/2022-01-20-gopher-setup.org
@@ -73,19 +73,19 @@ generate my gophermap:
- Clients can be finnicky and the protocl spec seems
to be not super well agreed upon by client
implimenters
- -- Some clients will not correctly parse info
+ - Some clients will not correctly parse info
lines if there is a " " after the i
- -- Some clients will seemingly ignore info lines
- -- Some clients don't mind if you don't have a "."
+ - Some clients will seemingly ignore info lines
+ - Some clients don't mind if you don't have a "."
char at the EOF, others seem to really care
- --- Apparently the "." at EOF is part of the spec,
- so it really should be there
- -- Some clients will automagically parse out any ANSI
+ - Apparently the "." at EOF is part of the spec,
+ so it really should be there
+ - Some clients will automagically parse out any ANSI
escape sequnces, others will interpret them correctly,
and others will barf them to the screen literally
- --- To my knowledge there is nothing in the spec for
- handling this, so client implementers can't be blamed
- -- Some gopher servers will helpfully auto fill lines in a
+ - To my knowledge there is nothing in the spec for
+ handling this, so client implementers can't be blamed
+ - Some gopher servers will helpfully auto fill lines in a
map that don't contain <TAB>$host<$TAB>$port. I learned
that motsognir will do this on a statically served map,
but (in hindsight, obviously), not a dynamically
diff --git a/2022-01-20-gopher-setup.pretty.html b/2022-01-20-gopher-setup.pretty.html
index 3d525ce..799468b 100644
--- a/2022-01-20-gopher-setup.pretty.html
+++ b/2022-01-20-gopher-setup.pretty.html
@@ -3,11 +3,10 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
-<!-- 2022-01-21 Fri 15:42 -->
+<!-- 2022-01-21 Fri 15:49 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title>
-<meta name="generator" content="Org mode" />
<style type="text/css">body{margin:40px
auto;max-width:900px;line-height:1.6;font-size:18px;color:#444;padding:0
10px}h1,h2,h3{line-height:1.2}</style>
@@ -62,19 +61,19 @@ auto;max-width:900px;line-height:1.6;font-size:18px;color:#444;padding:0
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
-<li><a href="#org38b106d">1. Setting up a Gopher Server</a></li>
-<li><a href="#org883f119">2. Basics</a></li>
-<li><a href="#org6abbb92">3. CGI</a>
+<li><a href="#org983ba01">1. Setting up a Gopher Server</a></li>
+<li><a href="#orgbb3aeb4">2. Basics</a></li>
+<li><a href="#org01c0017">3. CGI</a>
<ul>
-<li><a href="#org56a7a28">3.1. Footguns and Hangups</a></li>
-<li><a href="#org86dfa63">3.2. Helpful Patterns</a></li>
+<li><a href="#org9ca7470">3.1. Footguns and Hangups</a></li>
+<li><a href="#orgdec9391">3.2. Helpful Patterns</a></li>
</ul>
</li>
</ul>
</div>
</div>
-<div id="outline-container-org38b106d" class="outline-2">
-<h2 id="org38b106d"><span class="section-number-2">1</span> Setting up a Gopher Server</h2>
+<div id="outline-container-org983ba01" class="outline-2">
+<h2 id="org983ba01"><span class="section-number-2">1</span> Setting up a Gopher Server</h2>
<div class="outline-text-2" id="text-1">
<p>
Hey folks! In this post I'm going to talk a bit about setting
@@ -94,8 +93,8 @@ represent the better part of community knowledge, or
</div>
</div>
-<div id="outline-container-org883f119" class="outline-2">
-<h2 id="org883f119"><span class="section-number-2">2</span> Basics</h2>
+<div id="outline-container-orgbb3aeb4" class="outline-2">
+<h2 id="orgbb3aeb4"><span class="section-number-2">2</span> Basics</h2>
<div class="outline-text-2" id="text-2">
<p>
I'll just rattle these off quickly so that we don't need to spend
@@ -120,8 +119,8 @@ Checkout the following WWW links on the topic:
</div>
</div>
-<div id="outline-container-org6abbb92" class="outline-2">
-<h2 id="org6abbb92"><span class="section-number-2">3</span> CGI</h2>
+<div id="outline-container-org01c0017" class="outline-2">
+<h2 id="org01c0017"><span class="section-number-2">3</span> CGI</h2>
<div class="outline-text-2" id="text-3">
<p>
Because Gopher is a pretty simple protocol spec, I wanted to
@@ -178,8 +177,8 @@ this exercise to the reader.
</p>
</div>
-<div id="outline-container-org56a7a28" class="outline-3">
-<h3 id="org56a7a28"><span class="section-number-3">3.1</span> Footguns and Hangups</h3>
+<div id="outline-container-org9ca7470" class="outline-3">
+<h3 id="org9ca7470"><span class="section-number-3">3.1</span> Footguns and Hangups</h3>
<div class="outline-text-3" id="text-3-1">
<p>
A few things I learned trying to always dynamically
@@ -190,29 +189,35 @@ generate my gophermap:
<li>Clients can be finnicky and the protocl spec seems
to be not super well agreed upon by client
implimenters
-– Some clients will not correctly parse info
- lines if there is a " " after the i
-– Some clients will seemingly ignore info lines
-– Some clients don't mind if you don't have a "."
- char at the EOF, others seem to really care
- — Apparently the "." at EOF is part of the spec,
- so it really should be there
-– Some clients will automagically parse out any ANSI
- escape sequnces, others will interpret them correctly,
- and others will barf them to the screen literally
- — To my knowledge there is nothing in the spec for
- handling this, so client implementers can't be blamed
-– Some gopher servers will helpfully auto fill lines in a
- map that don't contain <TAB>$host<$TAB>$port. I learned
- that motsognir will do this on a statically served map,
- but (in hindsight, obviously), not a dynamically
- generated one, so make sure you're filling that out</li>
+<ul class="org-ul">
+<li>Some clients will not correctly parse info
+lines if there is a " " after the i</li>
+<li>Some clients will seemingly ignore info lines</li>
+<li>Some clients don't mind if you don't have a "."
+char at the EOF, others seem to really care
+<ul class="org-ul">
+<li>Apparently the "." at EOF is part of the spec,
+so it really should be there</li>
+</ul></li>
+<li>Some clients will automagically parse out any ANSI
+escape sequnces, others will interpret them correctly,
+and others will barf them to the screen literally
+<ul class="org-ul">
+<li>To my knowledge there is nothing in the spec for
+handling this, so client implementers can't be blamed</li>
+</ul></li>
+<li>Some gopher servers will helpfully auto fill lines in a
+map that don't contain <TAB>$host<$TAB>$port. I learned
+that motsognir will do this on a statically served map,
+but (in hindsight, obviously), not a dynamically
+generated one, so make sure you're filling that out</li>
+</ul></li>
</ul>
</div>
</div>
-<div id="outline-container-org86dfa63" class="outline-3">
-<h3 id="org86dfa63"><span class="section-number-3">3.2</span> Helpful Patterns</h3>
+<div id="outline-container-orgdec9391" class="outline-3">
+<h3 id="orgdec9391"><span class="section-number-3">3.2</span> Helpful Patterns</h3>
<div class="outline-text-3" id="text-3-2">
<p>
A few helpful patterns I've employed while writing my CGI
@@ -246,7 +251,7 @@ executing quickly, otherwise the client will be left waiting</li>
</div>
</div>
<div id="postamble" class="status">
-<p class="date">Created: 2022-01-21 Fri 15:42</p>
+<p class="date">Created: 2022-01-21 Fri 15:49</p>
</div>
</body>
</html>
diff --git a/style_hint.html b/style_hint.html
new file mode 100644
index 0000000..5974e63
--- /dev/null
+++ b/style_hint.html
@@ -0,0 +1,3 @@
+<style type="text/css">body{margin:40px
+auto;max-width:900px;line-height:1.6;font-size:18px;color:#444;padding:0
+10px}h1,h2,h3{line-height:1.2}</style>