all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: question regarding substitute* and #t
Date: Thu, 25 Jan 2018 22:53:49 -0500	[thread overview]
Message-ID: <877es58ecy.fsf@gmail.com> (raw)
In-Reply-To: <87bmhijs0p.fsf@igalia.com> (Andy Wingo's message of "Thu, 25 Jan 2018 08:51:02 +0100")

Andy Wingo <wingo@igalia.com> writes:

> On Thu 25 Jan 2018 06:31, Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Where does this `invoke' comes from? Geiser is unhelpful at finding it,
>> and it doesn't seem to be documented in the Guile Reference?
>
> https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00163.html

OK, so `invoke' is defined in (guix build utils), and it's docstring is:

   "Invoke PROGRAM with the given ARGS.  Raise an error if the exit code
   is non-zero; otherwise return #t."

Thanks,

Maxim

  reply	other threads:[~2018-01-26  3:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180124010802.18874.3012@vcs0.savannah.gnu.org>
     [not found] ` <20180124010803.590AF2068F@vcs0.savannah.gnu.org>
2018-01-24 12:06   ` Simplifications enabled by switching to 'invoke' Mark H Weaver
2018-01-24 12:14     ` question regarding substitute* and #t (was: Simplifications enabled by switching to 'invoke') Andy Wingo
2018-01-24 13:28       ` question regarding substitute* and #t Mark H Weaver
2018-01-24 15:20         ` Andy Wingo
2018-01-24 21:09           ` Kei Kebreau
2018-01-25  5:31           ` Maxim Cournoyer
2018-01-25  7:51             ` Andy Wingo
2018-01-26  3:53               ` Maxim Cournoyer [this message]
2018-01-25  8:31         ` Arun Isaac
2018-01-25 20:02           ` Mark H Weaver
2018-01-24 14:45       ` Hartmut Goebel
2018-01-24 15:27         ` Andy Wingo
2018-01-24 22:10           ` Ricardo Wurmus

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

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

  git send-email \
    --in-reply-to=877es58ecy.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.com \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.