***daviid is now known as Guest64483
***Guest64483 is now known as daviid
<daviid>guix-vits: will look into this asap, tx for the report ***dozzie_ is now known as dozzie
***jonsger1 is now known as jonsger
***jonsger1 is now known as jonsger
***jonsger1 is now known as jonsger
<Aurora_v_kosmose>Trying to determine if gc will do the right thing, or if I should explicitly close them. <manumanumanu>Aurora_v_kosmose: the GC will close any pipes left dangling <Aurora_v_kosmose>manumanumanu: Is there something to shell-quote a bit like Elisp's `shell-quote-argument'? <manumanumanu>Aurora_v_kosmose: do you have an example of the elisp version? <Aurora_v_kosmose>(shell-quote-argument "This one's a \"bit\" (forced) & all") => "This\\ one\\'s\\ a\\ \\\"bit\\\"\\ \\(forced\\)\\ \\&\\ all" <Aurora_v_kosmose>In the end... it may or may not be necessary depending on how open-pipe* passes the arguments. <manumanumanu>Aurora_v_kosmose: open-pipe* does not use the shell, so you don't need to quote them. open-pipe, however... <manumanumanu>but then you need to know the full path to whatever you are trying to run. <dsmith>Aurora_v_kosmose: gc usually happens because of memory pressure. Not really good to rely on that to clean up fd's. You could run out, depending on memory allocations.. <dsmith>I think it's a good idea to always clean up non-memory resources when you can.