| 7 May 2023 |
 uep | you might need a small extension or a program to watch dbus things and send relevant changes | 06:06:37 |
 @dre:imad.nyc | Yea, I saw a blog post about a systemd service that checks if the value changes, and it would change the config file, but nix doesn't let you just edit the .config file, and I'm not sure how to have a conditional that checks the dconf value | 06:07:51 |
| @dre:imad.nyc | A workaround that could be done is make a shell script that has 2 different config files only with the theme line changed, and the shell script itself checks if GNOME is in a dark mode or not, but this seems messy and I would rather try and do it within my nix configuration | 06:10:51 |
| uep | Nothing in nix is likely to do it, but whatever you end up with that does do it (even such a shell script) can of course be wrapped up into your nix config | 06:12:03 |
| uep | * Nothing in nix is likely to do it, but whatever you end up with that does do it (even such a shell script) can of course be wrapped up into your nix config to be installed and hooked into the right places (as a systemd service or gnome extension or whatever it ends up needing) | 06:12:49 |
| @dre:imad.nyc | In reply to@uep:matrix.org
Nothing in nix is likely to do it, but whatever you end up with that does do it (even such a shell script) can of course be wrapped up into your nix config I'll try and do this, but I had another thought. Is it possible to have nix create 2 separate derivations, say in this case light and dark, and have, for example, shell script, that would check the dconf value and switch between those? So if I called the program it would call different packages in the nix store depending on if it's dark mode or not? I'm not sure if this would be trivial to do within home manager. | 06:15:45 |
| uep | There's not a great benefit in adding that overhead, vs something that runs and makes the relevant settings based on the current value. It's just more framework and stuff to change as a way of pushing the same settings. | 06:17:25 |
| uep | If this is only about helix, rather than a more general issue, you could ask for an enhancement there, or write a wrapper that checks on startup | 06:19:15 |
| uep | (I don't know if you have long-running instances or start it frequently) | 06:19:58 |
| @dre:imad.nyc | In reply to@uep:matrix.org
If this is only about helix, rather than a more general issue, you could ask for an enhancement there, or write a wrapper that checks on startup I think this is more of a nix & gnome issue, since the solution for it exists outside of nix via just editing the file in ~/.confg. You're right about the overhead, and I know that putting in the shell script (or whatever) in my configuration itself is the same as making 2 derivations it feels more imperative than creating the 2 declarations. I'm not sure I can explain why though. I guess I'll look into it more but won't put too much effort. | 06:21:22 |
| @dre:imad.nyc | In reply to@uep:matrix.org
If this is only about helix, rather than a more general issue, you could ask for an enhancement there, or write a wrapper that checks on startup * I think this is more of a nix & gnome issue, since the solution for it exists outside of nix via just editing the file in ~/.config. You're right about the overhead, and I know that putting in the shell script (or whatever) in my configuration itself is the same as making 2 derivations it feels more imperative than creating the 2 declarations. I'm not sure I can explain why though. I guess I'll look into it more but won't put too much effort. | 06:21:32 |
| @dre:imad.nyc | * I think this is more of a nix & gnome issue, since the solution for it exists outside of nix via just editing the file in ~/.config. You're right about the overhead, and I know that putting in the shell script (or whatever) in my configuration itself is the same as making 2 derivations it feels more imperative than creating the 2 derivations. I'm not sure I can explain why though. I guess I'll look into it more but won't put too much effort. | 06:22:22 |
| @dre:imad.nyc | * I think this is more of a nix & gnome issue, since the solution for it exists outside of nix via just editing the file in ~/.config. You're right about the overhead, and I know that putting in the shell script (or whatever) in my configuration itself is the same as making 2 derivations but it feels more imperative than creating the 2 derivations. I'm not sure I can explain why though. I guess I'll look into it more but won't put too much effort. | 06:23:17 |
| uep | Getting nix involved at the time of switching seems way to heavy-weight, there's otherwise no reason it would be invoked. It can deploy both sets of configs, however you package them, in advance - but the thing that gets invoked by toggling dark mode should be much smaller, and just send a few dbus config changes, or swap config files / a symlink | 06:25:10 |
| uep | I think you want to change something in a helic config file, right? | 06:26:03 |
| uep | * I think you want to change something in a helix config file, right? | 06:26:12 |
| @dre:imad.nyc | In reply to@uep:matrix.org
I think you want to change something in a helic config file, right? Yes, and right now it's controlled by home-manager | 06:27:15 |
| @dre:imad.nyc | I think I have a solution, though, by a shell-script that reads the current dark mode and just having two config files that are identical and swapping between them. Helix has a flag to load in different config files. | 06:28:09 |
| uep | ah, i see. programs.helix.theme is a HM setting | 06:28:14 |
| uep | to generate that config. | 06:28:52 |
| @dre:imad.nyc | In reply to@uep:matrix.org
to generate that config. yup | 06:29:01 |
| uep | yeah, then sounds like a wrapper that chooses which config to pass helix each start could work well | 06:29:22 |
| uep | * yeah, then sounds like a wrapper that chooses which config to pass helix each start could work well enough | 06:29:28 |
| @dre:imad.nyc | yea, i think it should. Thanks! | 06:29:47 |
| uep | (is there an arg to pass that specific setting, rather than a file? Then you can just use the file HM generates, and override that one thing) | 06:39:01 |
|  @lotte:chir.rs joined the room. | 07:38:35 |
| @dre:imad.nyc | In reply to @uep:matrix.org
(is there an arg to pass that specific setting, rather than a file? Then you can just use the file HM generates, and override that one thing) Hmm, maybe I'll have to look into it later though | 15:32:04 |
|  WebSuperStar joined the room. | 19:57:16 |
| 8 May 2023 |
| @lotte:chir.rs changed their profile picture. | 07:09:59 |
 @js:ukvly.org | hey! for me login via GDM to my gnome session sometimes takes 2-3 attempts. I just end up at the login screen after entering the password. what's the best way to debug this? | 22:15:23 |
