From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 6784@debbugs.gnu.org
Subject: bug#6784: 24.0.50; cmdproxy incosistency with command pathnames
Date: Tue, 03 Aug 2010 20:21:13 +0300 [thread overview]
Message-ID: <83pqxzy5me.fsf@gnu.org> (raw)
In-Reply-To: <87iq3radvf.fsf@telefonica.net>
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Tue, 03 Aug 2010 17:56:52 +0200
> Cc:
>
> 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.
Please show the full recipe to reproduce this problem. You don't
invoke cmdproxy from the command line, do you?
> Maybe we should remove the CreateProcess method and do everything
> through the underlying shell.
That's not a good idea if the shell is command.com, for sure.
For cmd.exe, the problem is a lesser one, but it still exists; e.g.,
cmd.exe is limited to 4K long commands, while CreateProcess can handle
32K.
next prev parent reply other threads:[~2010-08-03 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:56 bug#6784: 24.0.50; cmdproxy incosistency with command pathnames Óscar Fuentes
2010-08-03 17:21 ` Eli Zaretskii [this message]
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=83pqxzy5me.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6784@debbugs.gnu.org \
--cc=ofv@wanadoo.es \
/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.