The documentation says to run M-x lisp-inferior-process, which doesn't exist. M-x inferior-lisp seems to be what was intended, and works.
Everyone also seems to need to setq-default hy-mode-inferior-lisp-command to something other than the default, and this is not documented, but should be. (setq-default hy-mode-inferior-lisp-command "python -i C:\\Python33\\Scripts\\hy-script.py") worked for me, but obviously it will be different for another operating system or Python version. Still, examples would help.
Edit:
I have determined that the problem with the default hy-mode-inferior-lisp-command is the PATH environment variable from inside Cygwin.
Assuming you use Cygwin to run EMACS, but not Python (e.g. so you can use some Python extensions that don't work in Cygwin), the default value will work if and only if you make sure the Python scripts folder is in your Bash path. It would be better to document this than the workaround.
It's still nice to be able to customize this setting, so I'm glad it's not hard coded. I like using "--spy" to see the generated Python code.
The documentation says to run
M-x lisp-inferior-process, which doesn't exist.M-x inferior-lispseems to be what was intended, and works.Everyone also seems to need to
setq-default hy-mode-inferior-lisp-commandto something other than the default, and this is not documented, but should be.(setq-default hy-mode-inferior-lisp-command "python -i C:\\Python33\\Scripts\\hy-script.py")worked for me, but obviously it will be different for another operating system or Python version. Still, examples would help.Edit: I have determined that the problem with the default hy-mode-inferior-lisp-command is the PATH environment variable from inside Cygwin.
Assuming you use Cygwin to run EMACS, but not Python (e.g. so you can use some Python extensions that don't work in Cygwin), the default value will work if and only if you make sure the Python scripts folder is in your Bash path. It would be better to document this than the workaround.
It's still nice to be able to customize this setting, so I'm glad it's not hard coded. I like using "--spy" to see the generated Python code.