| 22 Nov 2025 |
 jasi 🏳️⚧️ | * | 14:26:09 |
| 23 Nov 2025 |
 QuadRadical (Ping) | Did you set the dconf entry org.gnome.desktop.interface.monospace-font-name to "monospace"? | 19:24:38 |
|  catzzo joined the room. | 19:48:27 |
| 24 Nov 2025 |
 Capypara | I didn't, but yeah I guess that should be using my configured fontconfig font. But no that uses the default(?) monospace font. Which is better than no monospace font, so I'll take it for now. | 07:15:53 |
| Capypara | I should add that I think all apps affected are Flatpak apps. | 07:16:07 |
| Capypara | actually no, Fractal isn't 🤔 | 07:16:32 |
| QuadRadical (Ping) | oh, but i thought you were setting default monospace using fontconfig | 15:47:52 |
| Capypara | I was. Or am rather. I think that isn't working anymore actually. | 15:57:44 |
| Capypara | Since I noticed that all apps use the wrong font when I set it to monospace. Not just the GNOME apps. | 15:58:03 |
| Capypara | So I guess the home manager module for fontconfig isn't working / is not taking effect at least. | 15:58:27 |
| Capypara | Asking in the home manager channel... | 16:05:08 |
| QuadRadical (Ping) | Why not use the systemwide fontconfig? | 16:24:48 |
| QuadRadical (Ping) | e.g. this is what i have:
fonts = {
packages = with pkgs; [
inter
nerd-fonts.fira-code
];
fontconfig.defaultFonts = rec {
serif = [ "Inter" ];
sansSerif = serif;
monospace = [ "FiraCode Nerd Font" ];
};
};
| 16:25:23 |
| Capypara | Because I use a custom font and had issues with injecting that system wide before. But it's been over a year since I wrote this config, I can try again. | 16:26:16 |
| QuadRadical (Ping) | I don't understand what you mean | 16:28:57 |
| QuadRadical (Ping) | You mean, its not from a nix package? | 16:29:02 |
| Capypara | It is, but not from nixpkgs | 16:37:18 |
| Capypara | I package it myself | 16:37:22 |
| Capypara | It's a commercial font | 16:37:32 |
| QuadRadical (Ping) | should be fine still | 17:14:40 |
|  André Lima joined the room. | 21:01:39 |
| André Lima set a profile picture. | 21:10:25 |
| 25 Nov 2025 |
| Capypara | I have a fun new bug | 12:27:31 |
| Capypara | Not sure if this is NixOS specific, maybe somebody knows: When I open ddterm, a shell extension that opens an overlay terminal, and then close it again somehow in Electron and Java apps (or at least not Adwaita apps; maybe it's just in XWayland apps?) the last key I held while closing ddterm is stuck | 12:28:28 |
| Capypara | so for example, I open/close the terminal with CTRL+^. If I close it now, VSCode just spams ^ until I hold and release ^ again | 12:29:02 |
| Capypara | found it, mutter bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/4416 | 12:53:32 |
| Capypara | fixed in mutter 49.2 | 12:54:21 |
| Capypara | Is there a PR that includes mutter 49.2? Otherwise I'd open a PR | 12:54:59 |
| Capypara | is it even OK to update mutter on it's own or would that require other packages bumped as well? I'll just try for now. | 13:01:42 |
| Capypara | https://github.com/NixOS/nixpkgs/pull/464927 | 13:12:03 |
