-
Notifications
You must be signed in to change notification settings - Fork 347
haskell-process-load-file error (wrong-type-argument number-or-marker-p nil) when code has an error #1004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@bergey, is this because of your recent changes? |
I have the other computer which has an old version 20151102.256 and it works fine. |
@XinhuaZhang Can you run I haven't managed to reproduce this yet. When I have an error in my haskell file, @gracjan Maybe, but it's not obvious to me how. I didn't change |
@bergey After I run M-x toggle-debug-on-error and then run either haskell-process-load-file or haskell-process-load-or-reload there is no backtrace showing up. haskell-process-reload has the same problem. |
@bergey I think I have figured out the problem. The path to the file is something like "abc/Ubuntu One/def", there is a space between Ubuntu and One. There is no Ubuntu One any more, I am still doing my work in the directory somehow. |
Aha! Thanks for following up. I was stumped trying to reproduce the issue. Do you mean that you moved the Haskell file, and emacs doesn't know about the rename? Can we close this, or is there still a problem that we should fix? |
If there is no space in the path to the Haskell file, then it is fine. |
Supporting spaces in project paths is one of the things that we should do someday. |
^ I hope there is an issue for that? |
There is now :) |
Hello,
When I use
C-c C-l
, which ishaskell-process-load-file
command, and if there is an error in my code, this error shows. However, if the code is correct, then there is no such error.If I use
:l filename.hs
in the haskell buffer, it works correctly, no error at all.I wonder what is going on?
The text was updated successfully, but these errors were encountered: