1. 15
    1. 2

      I don’t know if it helps or is a better experience, but FreeBSD has VSCodium in ports: https://www.freshports.org/editors/vscode/

      1. 8

        It’s worth noting that the reason VS Code support on *BSD is not great is because Electron only officially supports platforms that Chromium supports and Google refuses to allow patches to support *BSD to be merged into Chromium, even with active maintainers and people willing to pay for and manage CI infrastructure.

      2. 3

        I should mention that in the article for sure! For me I prefer sticking to OpenBSD (I’m stubborn) - so I need to default on hacks 😛

        1. 3

          do you also own an electric car and heat your house with a coal furnace

          1. 4

            No electric car but my house is heated with propane and wood ;)

            1. 2

              it’s always something isn’t it

        2. 2

          ahh, I was hoping it could help with the port to OpenBSD. if not, that’s fine :)

    2. 2

      On disabling unveil: if you’d like to keep unveil enabled, and provide chromium access to a specific “development” path or similar, you can add a line in /etc/chromium/unveil.main that gives it read and/or write access to such a path:

      # allow access to development folder:
      ~/Code rwc

      More info in the pkg readme.

      Also may be useful to know: the default unveil paths are included in /usr/share/examples/chromium/unveil.main

      1. 2

        Also, I just remembered, chromium has a neat flag that will make it open a webpage without window decorations/ui. Useful for SPAs: --app="https://vscode.dev/".