summaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorbt <bt@web>2023-11-28 13:44:33 -0500
committerIkiWiki <ikiwiki.info>2023-11-28 13:44:33 -0500
commita482596d3bd415c53d30110b6b6f3bf0c6bb3606 (patch)
tree07fe6d2cadfaea1252f2514e666eaf6ed4cc756b /posts
parentf2bd58f73b12564b7b0424fe22aa51bdc77dd00c (diff)
Diffstat (limited to 'posts')
-rw-r--r--posts/vscode.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/posts/vscode.md b/posts/vscode.md
index 289d8ce..28505c7 100644
--- a/posts/vscode.md
+++ b/posts/vscode.md
@@ -1,6 +1,5 @@
-# Running VSCode in Chromium on OpenBSD
-
-2023-06-05
+[[!meta title="Running VSCode in Chromium on OpenBSD"]]
+[[!meta 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.
@@ -30,4 +29,4 @@ Success! We can avoid typing out these complex commands everytime we want to lau
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
+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!