From: "Park Hays" <park.notread@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: ipython/executable-find returns nil in Emacs 22.1 on XP
Date: Mon, 10 Sep 2007 20:42:29 -0600 [thread overview]
Message-ID: <b8efe0960709101942g61250f8s5328af453f6ee461@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Using Emacs 22.1 on Windows XP.
Particular file which precipitates this is in ipython.el, revision 2275.
The problem I'm experiencing is that the lisp which is, in effect,
(executable-find "ipython")
returns nil.
When I go to the command prompt (cmd.exe) I type "ipython" and the correct
behavior occurs--namely a python session with ipython starts. Therefore, I
assert that my path variables are correct.
I do not understand how executable-find goes about finding executables.
However, I suspect the problem is that the actual file executed when I type
"ipython" at the command prompt is named "ipython.py". XP has an
environment variable called "PATHEXT", which contains a semicolon-delimited
list of file extensions which are executed. I believe their is a
corresponding registry entry which tells the system how to execute scripts.
I don't know for certain, but I suspect a call to exec() will work
correctly--that is, invoke the script with its appropriate interpreter.
There is enough traffic on the newsgroup archives to suggest this may be the
cause of many problems people experience when trying to use emacs with
external applications. Or maybe it is just me :).
I love GNU Emacs, and having it on WinXP has been a delight. Thanks for all
your hard work!
-Park
[-- Attachment #2: Type: text/html, Size: 1429 bytes --]
next reply other threads:[~2007-09-11 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 2:42 Park Hays [this message]
2007-09-11 7:56 ` ipython/executable-find returns nil in Emacs 22.1 on XP Jason Rumney
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=b8efe0960709101942g61250f8s5328af453f6ee461@mail.gmail.com \
--to=park.notread@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
/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).