Please wait...
Despite its microsoftian origin, I do find myself enjoying VS Code for software development. Not without some tuning, of course -- the thing that really made it usable for me is the extension that makes the editor use vi (vim) keybindings. But one thing that kept being a problem was that I still habitually type "vi <filename>" in the terminal to start editing. And now you're editing in the terminal, not in the editor.
Yesterday I learned the fix. Put something like this in your ~/.bashrc or equivalent:
if [[ "$TERM_PROGRAM" == "vscode" ]]; then
alias vi='code'
alias vim='code'
fi
It turns out that if you run "code" and the name of a file from inside the terminal of a connected session, it won't start a new session; instead, it does-the-right-thing and opens that file in a new editor tab. What's more, this even works when VS Code is operating on a remote host through SSH, which happens to be how I always use it.
Not a linux expert here at all, but it seems pretty cool.
Nurb gave me a virtual desktop i could play with at his house. its just a webpage i hit and poof i get a desktop thing ( posting from there now ). Pretty neat. Going to try to learn some stuff. At least if i break it he can fix it for me :)
Yes.
NGINX -> guac -> Dedicated linux VM on proxmox. ( well the first 2 are dedicated VMs too, but you get the point ). I used to use it when i was still in the office most of the time.
May try again to rig up a 'wake on lan' detector to auto power up sleeping VMs. Did it once before, had issues reading the packets. Wasn't important, was just a random project, gave up. Might try it again.
And since i set it up for her, it of course runs Debian. lol. ( Bookworm, i have not updated my FAI images yet to Trixie )
Sun Sep 28 2025 20:29:25 UTC from IGnatius T FoobarCool, what's it running? Something attached to Guacamole?