[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#20744: shell-quote-argument in Emacs 24.5 and Emacs 25 on Windows ca

From: Da Zhang
Subject: bug#20744: shell-quote-argument in Emacs 24.5 and Emacs 25 on Windows cannot figure out path correctly
Date: Fri, 05 Jun 2015 17:05:37 -0400
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

I did a comparison of the subr.el and python.el between Emacs 24.3 and Emacs 24.5, and I found subr.el was not changed, but python.el was changed regarding the (shell-quote-argument) call as shown below:
I think this comparison could help localizing the cause of the change of behavior.

Da Zhang

On 6/5/2015 4:13 PM, Eli Zaretskii wrote:
Date: Fri, 05 Jun 2015 12:33:59 -0400
From: Da Zhang <address@hidden>

I use python mode (python.el) for some python programming. When I invoke
the command python-shell-send-buffer, my Emacs always reports "Searching
for program: no such file or directory,

I traced down the cause of this problem, and found the following lines
in python.el:
(defun python-shell-parse-command () ;FIXME: why name it "parse"?
"Calculate the string used to execute the inferior Python process."
;; FIXME: process-environment doesn't seem to be used anywhere within
;; this let.
(let ((process-environment (python-shell-calculate-process-environment))
(exec-path (python-shell-calculate-exec-path)))
(format "%s %s"
;; FIXME: Why executable-find?
(shell-quote-argument (executable-find python-shell-interpreter))

The function call 
(shell-quote-argument (executable-find python-shell-interpreter))
changed the path of my python interpreter from

I worked around this problem by replacing the function call
(shell-quote-argument (executable-find python-shell-interpreter))
(executable-find python-shell-interpreter) ;; edited by DZ on
2015/06/05: (shell-quote-argument) caused the problem of

To further analyze the problem, I found the function
shell-quote-argument defined in subr.el does not deal with the case when
bash from cygwin is used.
For the record, this is bug #20237.

I added the following lines in the cond statement, to solve the problem.
((and (eq system-type 'windows-nt) (if (string-match ".*cygwin.*"
(w32-shell-name)) t nil)) ;; DZ's edit on 6/5/2015
(if (equal argument "")
;; Quote everything except POSIX filename characters.
;; This should be safe enough even for really weird shells.
"\n" "'\n'"
(replace-regexp-in-string "[^-0-9a-zA-Z_./\n:]" "\\\\\\&" argument))))
I'm sorry, but I don't see how we can accept such a change: it means
that when the Cygwin Bash is used as the shell, the ':' character will
not be quoted, which I think could cause trouble in some cases.

Maybe some Bash expert could chime in and tell whether problems are
possible with Bash in this case.

Is there any way you could avoid using the Cygwin Bash as the shell
when running the native Windows build of Emacs?  That would make the
problem go away without any need for changes.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]