<buenouanq>if that's really the case, it still shouldn't be a big issue, you'll just have to learn to roll your own local guix package
<ryanwatkins>'dwm is customized through editing its source code, which makes it extremely fast
<ryanwatkins>and secure - it does not process any input data which isn’t known at compile time,
<ryanwatkins>except window titles and status text read from the root window’s name', I agree that I may have to specify a local guix package, I guess I just change the tarball location in my local spec?
<efraim>Or have a patch file that you throw into the source field
<buenouanq>or be a hero and take up the much need challenge of making guile-wm a fully fledged usable window manager
<ryanwatkins>buenouanq: this is my long term goal, I am just waiting for when I know guile good enough and know how to debug well enough :D
<buenouanq>ryanwatkins: the best way to learn a new language, is to dive head first into a complicated project requiring it :3
<ryanwatkins>buenouanq: I used to do this but I found that my biggest time was wasted driving my head into problems that were really just me missing a concept though I do agree with you, I have it installed and used it periodically but it would crash too often which I found seemed to be some problem with handling x11 errors
<buenouanq>make it so it uses wayland and we can abandon X for good
<ryanwatkins>buenouanq: that's what I thought about doing, I agree although I still think X is quite nice and fast, albeit old
<ryanwatkins>buenouanq: if I could stabilise it, I would actively develop on it but my wm would just crash too often and the stack trace really wasn't pointing to much, then i was spending time trying to figure out how to even deploy a fix and stuff, in which case I need to know more about guix and stuff..
<ryanwatkins>buenouanq: so in my head, I reconciled that I should fully understand guix, guile and unix (x11/wayland) a bit more first :P
<ryanwatkins>buenouanq: ofcourse, I want guile-wm to bring my dreams of a lisp machine closer haha
<buenouanq>I wish I had the time, skills/knowledge, or wherewithal to help you in this.
<ng0>I think the rxvt-unicode patch didn't work out, after reboot the name in at least one window manager is again "rxvt-unicode" for both.
<ng0>expected result when you install rxvt-unicode should be that you get two unique entries in menus for rxvt-unicode. Actual result after a reboot is two same entries (which call different, unique binaries). I've only added " (client)" to the urxvtc entry, assuming that this would work for .desktop files. do I have to escape the parens?
<quiliro>how can i establish guix to insist indefinitely if there are networking issues?
<thomasd>clacke[m]: about decentralization: because Guix is so malleable, it makes users much more independent from the distribution (it's super easy to add and/or modify packages etc). So that's another kind of decentralization. (not sure you were asking for ideas, I offer mine anyway :) )
<davexunit>my recommendation is to describe complete environments with 'guix environment', because otherwise if you try to use tools you already have on $PATH from something else you'll probably end up missing other important env vars
<amz3>indeed "guix environment guile-charting" works
<bavier1>Do we have any way to insert "activation code" into a users profile?
<bavier1>e.g. for a package that provides bash extensions, but needs some initialization code in .bash_profile or .bashrc
<davexunit>bavier1: I don't think so, but it sounds like a good thing to add along with the other profile things we do
<bavier1>davexunit: in debian they have a policy that packages cannot modify user's shell environments (iirc), but in guix, since packages are installed by users, I don't think we need to make that stance
<kyamashita>quiliro: The Claws Mail packaged in Guix might not have the "Fancy" plugin enabled.
<kyamashita>I just checked, and it is a configure flag. I suppose that the default for the fancy plugin is off.
<quiliro>kyamashita: thank you. how did you find out and what can i do to make it on?
<civodul>i wonder why we don't see any GSoC candidate this year
<civodul>usually there's always a few people emailing the list
<bavier1>davexunit: yes, like setting an alias or eval'ing the output of a command
<kyamashita>quiliro: I used `guix build -S claws-mail`, unpackaged the source and ran the Claws Mail's configure script with the `--help` option.
<kyamashita>quiliro: Also, it looks like it's on the packagers to compile and supply the plugins. The simple solution would be to add the appropriate flag upstream in the Guix package. If it turns out to be a small size difference, I'm sure things will go smoothly. Another option is getting a copy of the Guix repo, modifying Claws Mail's configure flags in its package defintion and installing Claws Mail from your local repo.