From 3f6a9546ec13063d0d5bdf21d30a93d3e8aa6050 Mon Sep 17 00:00:00 2001 From: Bradley Taunt Date: Tue, 2 Jul 2024 14:22:21 -0400 Subject: Rebuild changes based off latest barf --- build/posts/vscode/index.html | 59 ------------------------------------------- 1 file changed, 59 deletions(-) delete mode 100644 build/posts/vscode/index.html (limited to 'build/posts/vscode') diff --git a/build/posts/vscode/index.html b/build/posts/vscode/index.html deleted file mode 100644 index 86891bf..0000000 --- a/build/posts/vscode/index.html +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - - Running VSCode in Chromium on OpenBSD - - - - - - - -
-

Running VSCode in Chromium on OpenBSD

-

2023-06-05

-

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 hacky workaround to solve this problem.

-

VSCode in the Browser

-

I tried my best to build something like code-server locally and run that directly in my browser - but I failed miserably. Instead, I fell back on vscode.dev which is essentially a remote version of code-server.

-

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.

-
-

Note: The following assumes you have already installed chromium

-
-

First we need to disable unveil for Chromium. This will allow us to access our system files through vscode.dev using the “Open folder…” or “Open file…” commands without issue:

-
chrome --disable-unveil
-
-

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:

-
ENABLE_WASM=1 chrome --enable-wasm
-
-

Success! We can avoid typing out these complex commands everytime we want to launch our editor by setting up an alias (in my case via .zshrc):

-
alias vscode="ENABLE_WASM=1 chrome --enable-wasm --disable-unveil"
-
-

That’s it! Now I can just pop open VSCode on OpenBSD by simply running vscode in my terminal. Hopefully this can help others slowly transition over to OpenBSD - which you should do because it is amazing!

- \ No newline at end of file -- cgit v1.2.3-54-g00ecf