From: Ricardo Wurmus <rekado@elephly.net>
To: Brendan Tildesley <brendan.tildesley@gmail.com>
Cc: 40039@debbugs.gnu.org
Subject: bug#40039: 'wrap-script' introduces spurious argument
Date: Sun, 22 Mar 2020 11:27:30 +0100 [thread overview]
Message-ID: <87pnd4lm5p.fsf@elephly.net> (raw)
In-Reply-To: <2969f516-ca88-ffa6-dd65-f6a29682d42c@gmail.com>
Brendan Tildesley <brendan.tildesley@gmail.com> writes:
> It appears the repeated (car cl) results in the executable path
> getting sent to it's self as the first argument. I'm not sure how
> things managed to work up until now? I tested the following change and
> it fixed the one case I was using, but am not sure it is correct. why
> was the cons (car cl) there in the first place?
See the documentation of execl:
-- Scheme Procedure: execl filename arg ...
-- C Function: scm_execl (filename, args)
Executes the file named by FILENAME as a new process image. The
remaining arguments are supplied to the process; from a C program
they are accessible as the ‘argv’ argument to ‘main’.
Conventionally the first ARG is the same as FILENAME. All
arguments must be strings.
If ARG is missing, FILENAME is executed with a null argument list,
which may have system-dependent side-effects.
This procedure is currently implemented using the ‘execv’ system
call, but we call it ‘execl’ because of its Scheme calling
interface.
--
Ricardo
next prev parent reply other threads:[~2020-03-22 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 14:26 bug#40039: 'wrap-script' introduces spurious argument Ludovic Courtès
2020-03-22 0:53 ` Brendan Tildesley
2020-03-22 10:27 ` Ricardo Wurmus [this message]
2020-03-22 11:42 ` Brendan Tildesley
2020-09-13 2:35 ` Brendan Tildesley
2020-09-13 12:23 ` Ricardo Wurmus
2021-04-29 15:23 ` Brendan Tildesley via Bug reports for GNU Guix
2021-09-09 19:02 ` bug#40039: (No Subject) Attila Lendvai
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=87pnd4lm5p.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=40039@debbugs.gnu.org \
--cc=brendan.tildesley@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).