This may be an even more stupid answer: You can declare that multiline comment as a text inside an anonymous lambda and never call it. More seriously I don't know how to create multiline comments but you can select the whole paragraph and then M-x comment-region
Surprisingly enough I have borked Guix systems enough for me to need to chroot into the system via an installation image and repair from there. It's always a mystery to me whenever it happens. Usually, it's some system critical file (providence, activate-system.drv) that doesn't exist or is empty but Guix really believes that it is there and alive. So it's incredibly hard to switch generations when the file cannot be read and I cannot `guix gc` an alive file within the file system. Also, gc --verify repair doesn't work (perhaps because it needs to see the original scm file I used to reconfigure and it doesn't cache it?). In any case, I've been able to solve it, I have backups, and they haven't happened for a couple of months so maybe it was just a phase. It is, by far, more robust than other systems (if you lock your commits).
Guix needs to support macOS as a first-class platform if it wants to be taken seriously. The ideology that only "free" systems will be supported will be the death knell for Guix as it alienates people, prevents adoption, and does not invite open collaboration. I'd use it if it was actually cross platform.
"Prevents adoption and doesn't invite open collaboration". This is kind of the definition of macOS and the surrounding ecosystem, no? I don't think that Open Source should invest that much in macOS, just that some people don't have to give up their precious Macbooks, to feel that they are involved with Open Source. The way forward for Open Source is to create an experience on Linux that is not available elsewhere and make it compelling enough for people to switch, leaving their Windows and macOS behind.
No need for that cow manure, Guix is all about "Liberated systems" & MacOS does not conform to that philosophy & BTW, GNU & FOSS projects are doing fine enough without MacOS You're just making excuses so that your Precious Apple Mac doesn't go out of fashion
You have inspired me to daily drive Guix on my new laptop. Your guides have been invaluable; thank you for your hard work
Glad to hear it, thanks!
Can I ask a stupid question ?
How does one do multi-line comments in E-Lisp ?
This may be an even more stupid answer: You can declare that multiline comment as a text inside an anonymous lambda and never call it.
More seriously I don't know how to create multiline comments but you can select the whole paragraph and then M-x comment-region
Surprisingly enough I have borked Guix systems enough for me to need to chroot into the system via an installation image and repair from there. It's always a mystery to me whenever it happens. Usually, it's some system critical file (providence, activate-system.drv) that doesn't exist or is empty but Guix really believes that it is there and alive. So it's incredibly hard to switch generations when the file cannot be read and I cannot `guix gc` an alive file within the file system. Also, gc --verify repair doesn't work (perhaps because it needs to see the original scm file I used to reconfigure and it doesn't cache it?).
In any case, I've been able to solve it, I have backups, and they haven't happened for a couple of months so maybe it was just a phase. It is, by far, more robust than other systems (if you lock your commits).
Guix needs to support macOS as a first-class platform if it wants to be taken seriously. The ideology that only "free" systems will be supported will be the death knell for Guix as it alienates people, prevents adoption, and does not invite open collaboration. I'd use it if it was actually cross platform.
"Prevents adoption and doesn't invite open collaboration". This is kind of the definition of macOS and the surrounding ecosystem, no?
I don't think that Open Source should invest that much in macOS, just that some people don't have to give up their precious Macbooks, to feel that they are involved with Open Source.
The way forward for Open Source is to create an experience on Linux that is not available elsewhere and make it compelling enough for people to switch, leaving their Windows and macOS behind.
@@mitya Agreed. Focusing on macos is a step backwards. Open Source projects supporting proprietary operating systems is not the way to go.
No need for that cow manure, Guix is all about "Liberated systems" & MacOS does not conform to that philosophy
& BTW, GNU & FOSS projects are doing fine enough without MacOS
You're just making excuses so that your Precious Apple Mac doesn't go out of fashion
@@mitya You're missing the point. Many macOS developers/engineers also use "free" systems as do I and I want my tools to work everywhere not limited.