From: "Óscar Fuentes" <ofv@wanadoo.es>
To: 6784@debbugs.gnu.org
Subject: bug#6784: 24.0.50; cmdproxy incosistency with command pathnames
Date: Tue, 03 Aug 2010 17:56:52 +0200 [thread overview]
Message-ID: <87iq3radvf.fsf@telefonica.net> (raw)
A command path name that contains slashes (instead of backslashes) will
work fine with cmdproxy as far as it doesn't require to be executed
through a shell. Otherwise only backslashes work. Example:
cmdproxy.exe -c "c:/foo/bar.exe"
which executes bar.exe through CreateProces, works fine, but
cmdproxy.exe -c "c:/foo/bar.exe | zoo.exe"
which invokes the shell for executing the command, fails with an error
message that comes from cmd.exe and that says "c:" is not recognized as
a command.
OTOH,
cmdproxy.exe -c "c:\foo\bar.exe | zoo.exe"
works fine.
cmd.exe has no problem with commands that uses the slash as directory
separator, as this works OK:
cmd /c c:/foo/bar.exe
so the problem must be in cmdproxy, which probably splits the command as
"c:" "/foo/bar.exe"
and passes it as separate arguments to the shell.
Although this bug possibly is not hard to fix, maybe we should consider
the larger scenario: is it worth the trouble having two separate
execution paths on cmdproxy? Inconsistencies like this among the two
separate ways of executing commands may arise on the future, confusing
the users. Maybe we should remove the CreateProcess method and do
everything through the underlying shell.
next reply other threads:[~2010-08-03 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:56 Óscar Fuentes [this message]
2010-08-03 17:21 ` bug#6784: 24.0.50; cmdproxy incosistency with command pathnames Eli Zaretskii
2010-08-03 17:52 ` Óscar Fuentes
2010-08-03 18:15 ` Eli Zaretskii
2010-08-03 18:19 ` Laimonas Vėbra
2010-08-03 19:28 ` Eli Zaretskii
2010-08-03 20:15 ` Laimonas Vėbra
2010-08-03 20:57 ` Laimonas Vėbra
2010-08-04 3:08 ` Eli Zaretskii
2010-08-04 10:28 ` Laimonas Vėbra
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=87iq3radvf.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=6784@debbugs.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.
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.