Hi,
On Fri, 04 Nov 2022 at 00:34, jgart wrote:
> What determines which package gets built first in the following invocation?
>
> `guix build emacs-zig-mode zig`
It depends. :-) Usually, something like
guix thing stuff1 stuff2
is processed in that order: stuff2 then stuff1. Other said, the
jgart writes:
> I tried to upgrade vis but visidata was also upgraded... how comes?
>
> $ guix upgrade vis
> guix upgrade: warning: package 'emacs-vis' no longer exists
> The following packages will be upgraded:
>vis 0.7 → 0.8
>visidata (dependencies or package changed)
“guix upgr
jgart writes:
> does `guix lint` work inline in your editor as you type, with geiser?
I wouldn’t recommend it because some of the checks that “guix lint”
performs are really expensive. But generally you can run any kind of
check with flycheck.
--
Ricardo
On Fri Nov 4, 2022 at 12:45 AM GMT, jgart wrote:
> Interesting bug:
>
> It does build eventually but after taking a long time and emitting this
> warning:
>
> WARNING: Use of `load' in declarative module (guix ui). Add #:declarative?
> #f to your define-module invocation.
> WARNING: (guix build
Hi,
On Mon, 26 Sep 2022 at 10:58, Ludovic Courtès wrote:
> I think Csepp was on the right track though.
Thank you both for explaining. I hope to resume soon. :-)
Cheers,
simon
Heya,
On Fri Nov 4, 2022 at 9:49 AM GMT, zimoun wrote:
> Other said, the CLI is somehow parsed from right to left.
Probably because:
args: (pkg1 pkg2 pkg3)
cmds: ()
args: (pkg2 pkg3)
cmds: ((install . pkg1))
args: (pkg3)
cmds: ((install . pkg2)
(install . pkg1))
args: (
I am currently trying to extend guix's opensmtpd-service, so that users may
configure the service via records. As a part of this journey, I thought it would
be cool, if users could specify password records like the following, which would
auto encrypt the passwords in the resulting configuration
Hi,
On Fri, 04 Nov 2022 at 16:39, "(" wrote:
> On Fri Nov 4, 2022 at 9:49 AM GMT, zimoun wrote:
>> Other said, the CLI is somehow parsed from right to left.
>
> Probably because:
Well, it is because ’parse-command-line’ from (guix scripts), no?
> I suppose we could add a reverse in this proce
Hi again,
I had some data loss so I wasn't able to reply to this thread before.
I managed to make the tor-browser work in Guix proper, and I've
attached the script I used for that. It's hardcoded for i686 though so
it needs to be modified for x86_64.
Even if that works, there is a problematic is
