Simon Kohlmeyer
Simon Kohlmeyer
There's already an entry about Burma. As far as I can see, the library doesn't yet have an approach to handle situations like that.
Okay I had a look at the code and `burma.json` isn't loaded because it doesn't have a `name` entry. Since I'm just a passer-by, I can't speak on the intentions....
It's not quite that simple ``` voyd@boop> sudo -E bash -c 'echo $HOME' /home/voyd ``` the `-E` preserves the environment, but as far as I can tell, githud actively retrieves...
I'm personally running githud with a patch that changes the default to not start the daemon and that works for me, but I think I won't be the only person...
Would you be interested in contributions on that? If yes, I'd write a separate issue outlining the approach before I start coding. IIRC there's a library that allows config values...
I also added this patch to https://github.com/nixos/nixpkgs so I have it installed cleanly, so I'm not in a *personal* rush but I'm very much up to working in any requested...
Rebased on main, no change was needed
I think a great way to silence the warning would be a flag to opt into the new behaviour early :)
I definitely don't want to block this, but importing nixpkgs from the classic file makes stuff like `inputs.easy-purescript.inputs.nixpkgs.follows = "nixpkgs";` impossible
I think the problem with close is that there are two places where you would want to do that. Let's say you have a background thread that's listening on the...