Specified program for new process is a directory
Closed this issue · 6 comments
I have managed to follow the Pymacs installation instructions up to 2.5. It seems that my installation went fine, however, when I try M-x pymacs-eval with repr(2L**111) or M-x pymacs-load with os RET RET, I always end up getting a message saying 'Specified program for new process is a directory'. I am using Emacs 24.1.1 on Windows 7, along with Python 2.7.
Any help would be appreciated.
Hi. Hopefully, someone will be able to help you on this, as I do not use Windows, nor Emacs 24 yet, and cannot check.
François.
P.S. I quickly tried Emacs 24 two or three months ago, but had many issues with some Emacs packages I depend on, and did not have enough free time to address them all.
François, Your response is appreciated.
On Thu, Aug 30, 2012 at 9:53 PM, François Pinard
notifications@github.comwrote:
Hi. Hopefully, someone will be able to help you on this, as I do not use
Windows, nor Emacs 24 yet, and cannot check.François.
P.S. I quickly tried Emacs 24 two or three months ago, but had many issues
with some Emacs packages I depend on, and did not have enough free time to
address them all.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-8181283.
One possibility is to schedule a debugging session, using screen sharing, chat, or whatever. I'm not sure how productive it would be however. We would also need to find a common slot of free time, which I do not have plenty :-).
That's very kind from you. I made a post on Stack Overflow. Maybe someone
had this issue and knows what to do. Thank you again.
Jens
On Thu, Aug 30, 2012 at 10:11 PM, François Pinard
notifications@github.comwrote:
One possibility is to schedule a debugging session, using screen sharing,
chat, or whatever. I'm not sure how productive it would be however. We
would also need to find a common slot of free time, which I do not have
plenty :-).—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-8181494.
OK, I'm "closing" this issue. Do not hesitate to re-open it if you have anything new on this topic, that we should address. Keep happy!
Hi
I've been having similar warnings with other packages and my solution has been specifying the path for the binnary not the path for the bin directory.
Hope it helps