From: Eli Zaretskii <eliz@gnu.org>
To: Fabio Leimgruber <fabio.leimgruber@web.de>
Cc: 19817@debbugs.gnu.org
Subject: bug#19817: 24.4; cmdproxy fails on some .exe when given a path argument
Date: Sun, 08 Feb 2015 21:29:01 +0200 [thread overview]
Message-ID: <83r3u09p8i.fsf@gnu.org> (raw)
In-Reply-To: <trinity-5d5ce158-c2d8-4971-b864-49ecaefb4443-1423407448616@3capp-webde-bs14>
> From: "Fabio Leimgruber" <fabio.leimgruber@web.de>
> Date: Sun, 8 Feb 2015 15:57:28 +0100
>
> To reproduce, first copy `C:\Windows\System32\write.exe' to
> `C:\Windows\System32\write.test.exe'. Then from a Command Prompt
> (i.e. cmd.exe, I will use `$' for distinction nonetheless):
>
> $ cd D:\opt\emacs\libexec\emacs\24.4\x86_64-w64-mingw32
>
> $ cmdproxy.exe -c "\"write\" \"d:/asdf.txt\""
>
> works, whereas:
>
> $ cmdproxy.exe -c "\"write.test\" \"d:/asdf.txt\""
>
> fails with:
>
> 'write.test" "d:' is not recognized as an internal or external command,
> operable program or batch file.
You are not supposed to invoke cmdproxy directly, only via Emacs
functions that invoke shell commands. So please show a test case
which works with "write" or "write.exe" or "write.test.exe", but fails
with "write.test".
Also, why are you quoting file names that don't require any quotes?
next prev parent reply other threads:[~2015-02-08 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 14:57 bug#19817: 24.4; cmdproxy fails on some .exe when given a path argument Fabio Leimgruber
2015-02-08 19:29 ` Eli Zaretskii [this message]
2015-02-08 19:43 ` Eli Zaretskii
2015-02-09 14:46 ` Fabio Leimgruber
2015-02-09 17:43 ` Eli Zaretskii
2015-02-09 20:47 ` Fabio Leimgruber
2015-02-10 16:29 ` Eli Zaretskii
2015-02-13 22:34 ` Fabio Leimgruber
2015-02-14 8:43 ` Eli Zaretskii
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=83r3u09p8i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19817@debbugs.gnu.org \
--cc=fabio.leimgruber@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).