From: Eli Zaretskii <eliz@gnu.org>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Using `call-process-shell-command' in `process-lines'
Date: Mon, 26 Nov 2007 23:49:06 +0200 [thread overview]
Message-ID: <ubq9g3cfh.fsf@gnu.org> (raw)
In-Reply-To: <474B3946.5050404@gmail.com> (lennart.borgman@gmail.com)
> Date: Mon, 26 Nov 2007 22:23:18 +0100
> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
> CC: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
>
> (apply #'call-process "find.exe" nil
> (get-buffer-create "output")
> nil
> (list "c:/emacs-lisp/old/"
> "-name"
> (shell-quote-argument "*.el" )
> ))
>
> gives nothing in the "output" buffer and returns 0.
Well, ``return 0'' and ``fails'' are not exactly the same. The
original complaint by Juanma was that a non-zero status was returned.
Anyway, I see now that I missed something important: we already have a
wrapper for spawnve (w32proc.c:sys_spawnve), and it already tries to
quote arguments. In addition, it invokes the command thru cmdproxy.
So somewhere between the quoting code and cmdproxy there's a bug that
causes `find' to not find anything. AFAICS, quoting *.el with
shell-quote-argument causes it to wind up quoted in `find's argv[]
array, which explains why it finds nothing. Someone(tm) needs to
debug this.
next prev parent reply other threads:[~2007-11-26 21:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 14:11 Using `call-process-shell-command' in `process-lines' Juanma Barranquero
2007-11-26 15:35 ` Stefan Monnier
2007-11-26 16:01 ` Juanma Barranquero
2007-11-26 16:43 ` Stefan Monnier
2007-11-26 17:01 ` Juanma Barranquero
2007-11-26 17:28 ` Lennart Borgman (gmail)
2007-11-26 17:59 ` Juanma Barranquero
2007-11-26 19:58 ` Lennart Borgman (gmail)
2007-11-26 20:50 ` Eli Zaretskii
2007-11-26 21:25 ` Lennart Borgman (gmail)
2007-11-26 22:04 ` Eli Zaretskii
2007-11-26 22:16 ` Lennart Borgman (gmail)
2007-11-26 22:22 ` Eli Zaretskii
2007-11-26 22:39 ` Lennart Borgman (gmail)
2007-11-27 4:08 ` Eli Zaretskii
2007-11-27 22:34 ` Lennart Borgman (gmail)
2007-11-26 22:17 ` Eli Zaretskii
2007-11-26 22:35 ` Lennart Borgman (gmail)
2007-11-26 20:38 ` Eli Zaretskii
2007-11-26 20:23 ` Eli Zaretskii
2007-11-26 20:30 ` Eli Zaretskii
2007-11-26 20:31 ` Lennart Borgman (gmail)
2007-11-26 20:51 ` Eli Zaretskii
2007-11-26 21:08 ` Lennart Borgman (gmail)
2007-11-26 21:18 ` Eli Zaretskii
2007-11-26 21:23 ` Lennart Borgman (gmail)
2007-11-26 21:49 ` Eli Zaretskii [this message]
2007-11-26 22:17 ` Jason Rumney
2007-11-26 22:29 ` Eli Zaretskii
2007-11-26 22:30 ` Jason Rumney
2007-11-27 0:24 ` Juanma Barranquero
2007-11-26 22:33 ` Eli Zaretskii
2007-11-26 23:01 ` Jason Rumney
2007-11-27 4:13 ` Eli Zaretskii
2007-11-26 20:35 ` Stefan Monnier
2007-11-26 20:59 ` Eli Zaretskii
2007-11-26 21:18 ` Lennart Borgman (gmail)
2007-11-26 16:04 ` Juanma Barranquero
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=ubq9g3cfh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.