GNU bug report logs - #20237
Emacs built on Windows cannot figure out path correctly

Previous Next

Package: emacs;

Reported by: Da Zhang <zhangda82 <at> gmail.com>

Date: Tue, 31 Mar 2015 17:53:02 UTC

Severity: normal

Tags: notabug

Merged with 21421

Found in version 24.5

Done: Noam Postavsky <npostavs <at> users.sourceforge.net>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Da Zhang <zhangda82 <at> gmail.com>
Cc: 20237 <at> debbugs.gnu.org
Subject: bug#20237: Emacs built on Windows cannot figure out path correctly
Date: Sat, 04 Apr 2015 13:34:17 +0300
> Date: Wed, 01 Apr 2015 09:50:23 -0400
> From: Da Zhang <zhangda82 <at> gmail.com>
> CC: 20237 <at> debbugs.gnu.org
> 
> The commands I used were: 
> elpy-shell-send-region-or-buffer
> and
> elpy-shell-switch-to-shell
> 
> Under previous Emacs version 24.4.90, the same package and command worked fine. 

What does the following command display?

  M-: (python-shell-parse-command) RET

Also, what does this display?

  M-: (split-string-and-unquote (python-shell-parse-command)) RET

Please also note that you configured python.el to use the ipython
script as the interpreter, which AFAIK is not a .exe program, whereas
the error message you cited:

  apply: Searching for program: no such file or directory,
  c\:/Python27/Scripts/ipython.exe

seems to indicate that Emacs tries to look for a .exe program there,
or perhaps it doesn't recognize ipython the script as a program.  Not
sure if this is relevant to the problem.

Finally, can you set debug-on-error to t, load both python.el and
elpy.el as .el files (NOT .elc!), and then reproduce the problem and
show the full backtrace that the debugger displays?

Thanks.




This bug report was last modified 8 years and 354 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.