Dear François, Ricardo and divoplade,
This was indeed the issue, and the correct fix. Thank you for your
explanations. I'm not familiar with the notion of ports, coming from
languages that don't have them, but I see now how useful they are !
They're like the standard input/output of the shell, wit
Hi,
> (cut format "quake3-latest-pk3s/baseq3/pak~a.pk3" <>)
this is not correct.
“format” expects as its first argument a port or #true/#false, then it
takes the format string followed by values for each placeholder.
If you want to generate strings you should do
(cut format #false "quake3-
Le vendredi 12 mars 2021 à 17:53 +0100, e...@beaver-labs.com a écrit :
>(apply invoke "7z" "e" (assoc-ref %build-inputs "patch-
> data")
> (map (cut format "quake3-latest-
> pk3s/baseq3/pak~a.pk3" <>)
>(iota 8 1)))
Hello Edouard,
The first arg
Hello,
On Fri, Mar 12, 2021 at 05:53:27PM +0100, e...@beaver-labs.com wrote:
> Yet the build fail with the following error message:
>
> In ice-9/format.scm:
> 43:8 0 (format "quake3-latest-pk3s/baseq3/pak~a.pk3" 1)
>
> ice-9/format.scm:43:8: In procedure format:
> format: expected a string
Dear Guixers,
In a channel-that-should-not-be-named, there is the following snippet
(apply invoke "7z" "e" (assoc-ref %build-inputs "patch-data")
(map (cut format "quake3-latest-pk3s/baseq3/pak~a.pk3" <>)
(iota 8 1)))
Which, as far as my limite
