diff options
Diffstat (limited to 'build/vscode')
| -rw-r--r-- | build/vscode/index.html | 55 |
1 files changed, 55 insertions, 0 deletions
diff --git a/build/vscode/index.html b/build/vscode/index.html new file mode 100644 index 0000000..4f01018 --- /dev/null +++ b/build/vscode/index.html @@ -0,0 +1,55 @@ +<!doctype html> +<html lang="en" id="top"> +<head> + <meta charset="utf-8"> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <link rel="icon" href="data:,"> + <title>Running VSCode in Chromium on OpenBSD</title> + <link href="https://bt.ht/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> + <style>*{box-sizing:border-box;}body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{overflow:auto;}table{text-align:left;width:100%;}</style> +</head> + +<nav> + <a href="#menu">Menu ↓</a> +</nav> + +<main> +<h1>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'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>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 "Open folder..." or "Open file..." 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't. Syntax highlighting does not work without enabling WASM/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'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> + <ul id="menu"> + <li><a href="/">Home</a></li> + <li><a href="/projects">Projects</a></li> + <li><a href="/uses">Uses</a></li> + <li><a href="/wiki">Wiki</a></li> + <li><a href="/resume">Resume</a></li> + <li><a href="/colophon">Colophon</a></li> + <li><a href="/now">Now</a></li> + <li><a href="/donate">Donate</a></li> + <li><a href="/atom.xml">RSS</a></li> + <li><a href="#top">↑ Top of the page</a></li> + </ul> + <small> + Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br> + Maintained with ♥ for the web. <br> + Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> & <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br> + The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>. + </small> +</footer>
\ No newline at end of file |