Gitconfig not used in vscodium-fhs

Help
1

I have installed vscodium-fhsas a system package, as well as git via:

  programs.git = {
    enable = true;
    config = {
     ...
    }
  }

which will place the config to /etc/gitconfig.

Now vscodium-fsh doesn’t seem to be able to load this config as I can’t use the built-in git functionality nor any git command via the built-in terminal (both complaining about missing configuraiton). I have already tried to liink /etc/gitconfig to ~/.gitconfigbut this does also not satisfy vscodium-fhs. Does someone have an idea how to fix it? I’m using NixOS 25.11.

2

Have you tried non-FHS vscode?

Is there anything in the logs when you try to use git?

And why do you use FHS in the first place? Except for a very limited set of usecases it causes more trouble than it solves.

3

I’m currently switching to NixOS and didn’t want to configure every extension via nix yet (that’s what the wiki page makes it sound like) and do a shortcut getting a suitable setup running for me.

4

I’m in exactly the same situation.

Git when run inside vscode-fhs can not see its own global config file. If you try and open the file with its file browser, you can’t: I think that file is simply hidden from it

cat /etc/gitconfig

cat: /etc/gitconfig: No such file or directory

That finds the file just fine from a non-vscode terminal.

When I read:

Wrapped variant of vscodium which launches in a FHS compatible environment, should allow for easy usage of extensions without nix-specific modifications

That sounds like an easy way to get my extensions working for now. The fact it breaks global git config, and the ability to elevate with sudo (and I have no idea what else) and the ability to open some files isn’t very clear.

Regardless, I worked around this for now by using a different editor (since vscode fails to open that file) to open my /etc/gitconfig and copy the contents into the git config for my local repo for now.

Longer term, I think I want to migrate away from the fhs version, but I’d like to know what its supposed to do so I can tell if these issues are intended behaviors or bugs.

Its unclear what “FHS” means (I think its Filesystem Hierarchy Standard, but its unclear what standard that is referring to or how thats intended to impact vscode). Maybe this is a bug on the FHS wrapper, maybe its a feature of it. I can’t find any way to tell from NixOS Search since the description doesn’t say, and the linked homepage doesn’t include the fhs wrapper. I guess to figure it out we are supposed to read nixpkgs/pkgs/applications/editors/vscode/generic.nix at 5b4f72e1705a63aace42900610c4db82cb4af0ec · NixOS/nixpkgs · GitHub ?

Perhaps Documentation request: FHS · Issue #83791 · NixOS/nixpkgs · GitHub covers documenting what FHS really means here?

Is the correct action here to file a bug in Issues · NixOS/nixpkgs · GitHub pointing out that the description string for vscode-fhs and vscodium-fhs should better document what they are (for example either document or link to a page which documents things like what FHS means, and the implications of it). Then if that gets addressed, determine if the behavior we see, like git config not working, is a bug or not based on that documentation, and if its a bug report it?