Install VSCodium and make host .application file #86
Conversation
justinmichaud
commented
Jan 16, 2025
justinmichaud
commented
- Work around lldb python issues
- Install VSCodium by default
- Add helpful clangd default settings
- Make VSCode .application file by default
| "editorWhitespace.background": "#FF0000" | ||
| }, | ||
| "terminal.integrated.allowChords": false, | ||
| } |
There was a problem hiding this comment.
Some of these are pretty arbitrary. I like the clangd.arguments but maybe lets move this to a different PR to discuss.
There was a problem hiding this comment.
The clangd and fg/bg colours are important for our style guidelines, but I removed the rest.
There was a problem hiding this comment.
Oh you just mean to more easily visualize whitespace.
I've never needed that and don't think I'd want it by default. I'll check how it looks.
There was a problem hiding this comment.
I'm going to vote no on this, I think it would annoy most people.
There was a problem hiding this comment.
Oh shoot, it doesn't look like that for me. It is only supposed to display trailing whitespace
There was a problem hiding this comment.
Some other setting is involved. It would be best to keep these PRs small, I'd remove this change here and it can be discussed on its own.
justinmichaud
force-pushed
the
vscodium-xdg
branch
from
728c692 to
f5cd9f4
Compare
|
Thank you for the review, everything has been updated! |
- Add helpful clangd default settings - Make VSCode .application file by default
justinmichaud
force-pushed
the
vscodium-xdg
branch
from
f5cd9f4 to
3e1d171
Compare
| install_extension() { | ||
|
|
||
| sudo chown "${USER}" "${HOME}/.config" |
There was a problem hiding this comment.
How would .config be owned by a different user?
There was a problem hiding this comment.
Maybe this was an idiosyncrasy of my setup, let's remove it and see if it comes up again
There was a problem hiding this comment.
This is needed if you run this script from your firstrun script. It seems it runs as root. I guess I can change my firstrun script to run as the container user
There was a problem hiding this comment.
What I said makes no sense, since we use $USER here
There was a problem hiding this comment.
It looks like systemd makes the config path? At the very least, some files in ~/.config/systemd appear to be owned by root.
There was a problem hiding this comment.
This is needed if you run this script from your firstrun script. It seems it runs as root. I guess I can change my firstrun script to run as the container user
It very explicitly runs as your user:
There was a problem hiding this comment.
It looks like systemd makes the config path?
While podman supports systemd, we don't use it, and I'd expect systemd knows nothing at all about the containers home.
There was a problem hiding this comment.
Yeah, this is confusing to me, although .config is definitely owned by root. In particular, so is .config/systemd, which seems to come from nowhere. Do you have any ideas how I can start debugging this?
