From: Eli Zaretskii <eliz@gnu.org>
To: sdl.web@gmail.com, 9792@debbugs.gnu.org
Subject: bug#9792: 24.0.50; process-file and space in filename
Date: Thu, 20 Oct 2011 13:00:18 +0200 [thread overview]
Message-ID: <8362jkszb1.fsf@gnu.org> (raw)
In-Reply-To: <83aa8wt1yv.fsf@gnu.org>
> Date: Thu, 20 Oct 2011 12:02:48 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 9792@debbugs.gnu.org
>
> > But I can C-u M-C-x process-file and get a backtrace like this one:
> > http://paste.pound-python.org/show/13964 if that is helpful.
>
> Assuming that process-file is called with the name of the program
> being just "git", with no leading directories, it sounds like the
> problem is born inside call-process and its subroutines; I will have a
> look.
The problem happens when both of the following conditions are true:
. the command being invoked is a batch file (git.cmd in this case)
. the directory where it lives included parentheses
I cannot find a workable solution for this situation; the error
happens even if the batch file is invoked via the system shell.
Suggestions for solving this are welcome. The relevant function is
w32proc.c:sys_spawnve.
Unless someone can suggest how to fix this, I'm inclined to tag this
problem as "wontfix", and suggest that Windows users do not install
such commands in a directory whose name includes parentheses.
next prev parent reply other threads:[~2011-10-20 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 3:43 bug#9792: 24.0.50; process-file and space in filename Leo
2011-10-19 7:36 ` Eli Zaretskii
2011-10-19 17:23 ` Leo
2011-10-19 18:02 ` Eli Zaretskii
2011-10-20 5:07 ` Leo
2011-10-20 7:12 ` Michael Albinus
2011-10-20 9:14 ` Leo
2011-10-20 10:02 ` Eli Zaretskii
2011-10-20 11:00 ` Eli Zaretskii [this message]
2011-10-21 1:27 ` Leo
2011-10-21 7:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8362jkszb1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9792@debbugs.gnu.org \
--cc=sdl.web@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.