<efraim>Never tried it, but I've heard the emacs one (exwm?) works fairly well
<wigust>emacsomancer: bind:utils package contains a dig program. However I think that currently there is no way to discover file or program belongs to package unless it's mentioned in a package description.
<rekado>sometimes I apply the patches to see more context
<rekado>sometimes I just read the mail containing the diff and look up context separately.
<rekado>I wonder if there’s an Emacs mode to assist this kind of workflow.
<rekado>civodul: one thing about the new (guix status) that I don’t understand is how the communication between the daemon and the client works.
<rekado>civodul: does the client just have a single port to the daemon’s stderr, even if there are multiple things going on at the same time?
<rekado>one problem with the code in “master” is that it has no idea of what came before the current chunk of text, so we couldn’t even properly colourise the multiple lines of hash mismatch errors.
<rekado>this might still be a problem with the new code, but I have yet to test this.
<civodul>rekado: regarding workflow, i do on a case-by-case basis as you describe
<civodul>rekado: fundamentally there's still just a single build log port, meaning that for max-jobs > 1 things might be intermingled (except "@ build-succeeded" and other things written by the daemon itself, which are guaranteed to be "atomic")
<civodul>the problem with the multiple-line hash mismatch error, i don't know
<roptat>I tried to change my guix-daemon.service to run guix from /root/.config, but I get /root/.config/guix/current/bin/guix: Permission denied
<rekado>civodul: the multiline hash mismatch error is weird: it’s printed twice; once it is received as a big multiline string with newline characters; another time it’s just build log output received as separate strings.
<roptat>more precisely /gnu/store/sf84mb2y5vcykwq9fv02l2nipp34qng2-guix-daemon-0.15.0-3.3d43017/libexec/guix/download: line 8: /root/.config/guix/current/bin/guix: Permission denied
<rekado>the implementation on “master” has no way to associate the following lines with the first line, so it doesn’t colourise them.
<sirgazil>I wanted to mention also that I had a previous version of guix installed, and deleted /gnu and /var/guix before running the installation script.
<lrochfort>Hi all. I'm modifying my config.scm for the first time. I've read the "Services" section of the Info manual, but still don't fully understand what use-package-modules and use-service-modules do.
<ng0>i can't really push, so i can't share what I have in context. given that %nginx-config exists, I think the following could be a problem as I am moving from nginx where it used to have #:config-file.