From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Using `call-process-shell-command' in `process-lines'
Date: Mon, 26 Nov 2007 11:43:13 -0500 [thread overview]
Message-ID: <jwv3autnenv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f7ccd24b0711260801o61c6180bu33a46c260b8fe015@mail.gmail.com> (Juanma Barranquero's message of "Mon, 26 Nov 2007 17:01:12 +0100")
>> Please describe the actual problem so we can find another solution
>> to it.
> There are two parts: the first one is hardcoded "find" and "grep"
> commands, which I want to replace with find-program and grep-command.
> I suppose you won't oppose to that.
> As for the problem:
> - Running check-declare-directory as it is now (after changing "find"
> to `find-program' and "grep" to `grep-program' and suitably setting
> the variables):
> process-lines: c:/bin/gnuwin32/bin/find.exe exited with status 1
> process-lines: c:/bin/msys/bin/find.exe exited with status 1
> This is with MSYS' find ("GNU find version 4.1") and GnuWin32's find
> ("GNU find version 4.2.20").
I have no idea what this means. Could you expand on it?
> - After I wrap "*.el" and "^[\t ]*(check-function" in `shell-quote-argument':
> Both programs return succesfully without finding any *.el file (root
> is c:/emacs/trunk/lisp/ when I invoke check-declare-directory).
Why would you want to wrap them? They're not passed to a shell!
Stefan
next prev parent reply other threads:[~2007-11-26 16:43 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 [this message]
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
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=jwv3autnenv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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 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.