From 16d28628aca9b2d356de31c319f5e7bc0f5b2b02 Mon Sep 17 00:00:00 2001
From: Bradley Taunt <bt@btxx.org>
Date: Sat, 8 Jun 2024 13:43:37 -0400
Subject: Remove incorrectly generated files, fix up markdown articles

---
 build/vscode/index.html | 16 ++--------------
 1 file changed, 2 insertions(+), 14 deletions(-)

(limited to 'build/vscode')
diff --git a/build/vscode/index.html b/build/vscode/index.html
index 30c17de..92c54fb 100644
--- a/build/vscode/index.html
+++ b/build/vscode/index.html
@@ -3,11 +3,12 @@
 <head>
 	<meta charset="utf-8">
 	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<meta name="color-scheme" content="dark light">
 	<link rel="icon" href="data:,">
 	<title>Running VSCode in Chromium on OpenBSD</title>
 	<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
 	<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
-<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
 </head>
 
 <nav>
@@ -16,36 +17,23 @@
 
 <main>
 <h1 id="running-vscode-in-chromium-on-openbsd">Running VSCode in Chromium on OpenBSD</h1>
-
 <p>2023-06-05</p>
-
 <p>VSCode and its many variations are not available on OpenBSD. This doesn&#8217;t cause issue with many OpenBSD users, but those making the jump from Linux might miss access to such a popular editor. Lucky for us, there is a <em>hacky</em> workaround to solve this problem.</p>
-
 <h2 id="vscode-in-the-browser">VSCode in the Browser</h2>
-
 <p>I tried my best to build something like <code>code-server</code> locally and run that directly in my browser - but I failed miserably. Instead, I fell back on <a href="https://vscode.dev">vscode.dev</a> which is essentially a remote version of <code>code-server</code>.</p>
-
 <p>Getting things to work seamlessly proved a little more challenging. I found the best performance was running everything through Chromium with special parameters enabled on launch.</p>
-
 <blockquote>
 <p><strong>Note:</strong> The following assumes you have already installed <code>chromium</code></p>
 </blockquote>
-
 <p>First we need to disable <a href="https://man.openbsd.org/unveil.2">unveil</a> for Chromium. This will allow us to access our system files through <a href="https://vscode.dev">vscode.dev</a> using the &#8220;Open folder&#8230;&#8221; or &#8220;Open file&#8230;&#8221; commands without issue:</p>
-
 <pre><code>chrome --disable-unveil
 </code></pre>
-
 <p>Everything should work pretty solid right out the box now - except it doesn&#8217;t. Syntax highlighting does not work without enabling WASM&#47;WebAssembly. Your experience might be different, but I had to include the following when launching Chromium from the terminal:</p>
-
 <pre><code>ENABLE_WASM=1 chrome --enable-wasm
 </code></pre>
-
 <p>Success! We can avoid typing out these complex commands everytime we want to launch our editor by setting up an <code>alias</code> (in my case via <code>.zshrc</code>):</p>
-
 <pre><code>alias vscode="ENABLE_WASM=1 chrome --enable-wasm --disable-unveil"
 </code></pre>
-
 <p>That&#8217;s it! Now I can just pop open VSCode on OpenBSD by simply running <code>vscode</code> in my terminal. Hopefully this can help others slowly transition over to OpenBSD - which you should do because it is amazing!</p>
 <footer role="contentinfo">
     <h2>Menu Navigation</h2>
-- 
cgit v1.2.3-54-g00ecf

