unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Edouard Klein <edou@rdklein.fr>
To: help-guix@gnu.org
Subject: Re: Error with guile function format
Date: Sat, 13 Mar 2021 00:33:39 +0100	[thread overview]
Message-ID: <87pn04ne0c.fsf@rdklein.fr> (raw)
In-Reply-To: <87sg50nwjc.fsf@rdklein.fr>

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, with redirections,
but for any function inside the program. Awesome :)

Thank you very much !

I've submitted a patch upstream (and also played quake 3 for the first
time in ~15 years :) oh the memories)

Cheers,

Edouard.


edk@beaver-labs.com writes:

> 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 limited knowledge of Guile goes, is correct.
>
> 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 for format string 1
>
>
> The first argument to format is a string, so I don't understand the
> fuss.
>
> Any idea would be welcome :)
>
> Thanks !
>
> Edouard.



      parent reply	other threads:[~2021-03-12 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 16:53 Error with guile function format edk
2021-03-12 17:27 ` JOULAUD François
2021-03-12 17:40 ` divoplade
2021-03-12 18:23 ` Ricardo Wurmus
2021-03-12 23:33 ` Edouard Klein [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn04ne0c.fsf@rdklein.fr \
    --to=edou@rdklein.fr \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).