diff options
| author | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:28:49 -0400 |
|---|---|---|
| committer | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:28:49 -0400 |
| commit | dc6db80fa72286704849ef61ee0e5ccb5841cb09 (patch) | |
| tree | 9235d796229d49211c27a07b9d18585d503baa94 /_posts/2023-06-05-vscode.md | |
| parent | 088c87bcb58be576308da503d4f11a68843c5013 (diff) | |
Conversion to barf for testing purposes
Diffstat (limited to '_posts/2023-06-05-vscode.md')
| -rw-r--r-- | _posts/2023-06-05-vscode.md | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/_posts/2023-06-05-vscode.md b/_posts/2023-06-05-vscode.md deleted file mode 100644 index 239a308..0000000 --- a/_posts/2023-06-05-vscode.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -layout: post -title: "Running VSCode in Chromium on OpenBSD" -date: 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](https://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](https://man.openbsd.org/unveil.2) for Chromium. This will allow us to access our system files through [vscode.dev](https://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! |