00:43:54 tony.c: dkms 00:44:12 Sean T: DKMS 😢 00:45:33 Daniel S: Invited by Robert Citek. 01:06:53 james Conroy: ever mess with gitpod.io ? 01:09:50 Sean T: Dev Containers could be another 'one click' type of thing. Your students would have to have Docker installed though. That could be a deal-breaker or some older chromebooks 01:28:52 Sean T: https://docs.github.com/en/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#monthly-included-storage-and-core-hours-for-personal-accounts 01:33:24 Sean T: VSCode's keybind customizability is on par with Emacs and VIM 01:35:42 Sean T: I can't pull up the command palette in code spaces 01:40:15 Scott Granneman: “VS Code's container configuration is stored in a devcontainer.json file. This file is similar to the launch.json file for debugging configurations, but is used for launching (or attaching to) your development container instead. The dev container configuration is either located under .devcontainer/devcontainer.json or stored as a .devcontainer.json file (note the dot-prefix) in the root of your project.” https://code.visualstudio.com/docs/devcontainers/create-dev-container 01:43:04 Sean T: I watched this presentation on dev containers. It seemed pretty interesting. https://www.youtube.com/watch?v=HV7LJ_LUZ5A 01:50:10 Scott Granneman: Not sure if these will help Robert, but… * Emacs in the Browser Using Codespaces - https://notes.alexkehayias.com/emacs-in-the-browser-using-codespaces/ * Use Emacs key bindings in VS Code - https://mrcoles.com/emacs-key-bindings-vscode/ 01:52:10 Scott Granneman: https://github.com/rsgranne/grannepack-web-dev-settings 02:01:58 Sean T: exec into it? 02:23:21 Ron BC: I thought MS stored their stuff in some git-based tool that acts more like a file system? Saves cloning all Windows just to tweak the calculator, for example.