From: Arthur Miller <arthur.miller@live.com>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: gnu-emacs-help@gnu.org
Subject: Re: Why is this not working (apply + call-process + list of string args)?
Date: Thu, 15 Sep 2022 23:43:42 +0200 [thread overview]
Message-ID: <AM9PR09MB49772207C48B8C42E5894BD696499@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <b875afd4-8022-4a16-9791-0e4cbc5c1d1f@BN8NAM04FT028.eop-NAM04.prod.protection.outlook.com> (Bruno Barbier's message of "Thu, 15 Sep 2022 19:00:44 +0200")
Bruno Barbier <brubar.cs@gmail.com> writes:
> Arthur Miller <arthur.miller@live.com> writes:
>
>> I just wonder if someone can explain exact what is going on here:
>>
>> I have a list of strings of arruments I try to pass to configure script. It
>> looks something like this:
>>
>> #+begin_src emacs-lisp
>> (defvar args
>> '("--with-native-compilation "
>> "--with-x "
>> "--with-x-toolkit=no "
>> "--without-gconf "
>> "--without-gsettings "
>> "--with-cairo "
>> "--without-toolkit-scroll-bars "
>> "--with-xinput2 "
>> "--without-included-regex "
>> "--without-compress-install "))
>>
>> (defun configure (&rest args)
>> (apply #'call-process
>> (expand-file-name "./configure")
>> nil build-log nil args))
>>
>> (apply #'configure args)
>> #end_src
>>
>> However it does not work, configure script seems to see wrong arguments.
>
> Why do you have a space after each option ?
Space was there because I was assembling a command to run another
Emacs process asynchronously, but I have solved it now differently. Thanks for
the help, spaces were indeed the problem.
prev parent reply other threads:[~2022-09-15 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 13:56 Why is this not working (apply + call-process + list of string args)? Arthur Miller
2022-09-15 15:12 ` Jean Louis
2022-09-15 21:37 ` Arthur Miller
2022-09-15 22:04 ` Jean Louis
2022-09-15 23:16 ` Arthur Miller
2022-09-15 17:00 ` Bruno Barbier
[not found] ` <b875afd4-8022-4a16-9791-0e4cbc5c1d1f@BN8NAM04FT028.eop-NAM04.prod.protection.outlook.com>
2022-09-15 21:43 ` Arthur Miller [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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM9PR09MB49772207C48B8C42E5894BD696499@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=brubar.cs@gmail.com \
--cc=gnu-emacs-help@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).