-
Notifications
You must be signed in to change notification settings - Fork 347
PowerShell hangs on haskell-process-generate-tags #609
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
Well, I like it. But then I'm not using Windows...
I guess the powershell trick is from times before when hasktags was
recursive in itself.
One thing: can you check if paths with spaces in them work for the %s
substitution? Windows likes spaces and we need to support that. Just put
your project inside C:\Documents and Settings and that should give you a
clue if this works or not.
|
Good catch. I will try this tomorrow and make a pull request if it works. |
I had the same problem, the powershell command caused an error. It also caused the exact same error if I typed the command in the powershell myself, though. Maybe it depends on the system environment? Paths with spaces don't work ("warning: no files found!"), but I could fix this by escaping the paths with quotes.
The escaping is kind of a hack of course, but I'm way too much of a newbie in Emacs and LISP to try a more elegant solution. I only just noticed because I don't have to restart the process all the time anymore: Is it correct that files aren't automatically loaded into the REPL when saved? Or am I doing something wrong? |
Double quotes are good enough for windows provided the last char in path is
not backslash.
I do not know how to answers your question.
|
@TimoFreiberg , looks like you're faster than me 👍 Anyway, about your question:
You have to cal |
Wait, where is the pull request? |
Recreated it, I thought I did something wrong before. |
Now it works. Thanks! |
Hello! I recently updated
haskell-mode
and noticed that the tag generation (when I save/reload a file) gets "locked" into powershell. I don't know why, bu when the current command is run inside emacs:Everything just freezes. The equivalent command, in the shell itself, does not hang.
Why we must do this with powershell? Is there a specific reason to not use
hasktags
directly?On my configuration, I changed the above line with:
And the result looks the same to me (it's even recursive).
If the above solution is acceptable, I can send a patch/pull request later.
Related:
#49
#447
The text was updated successfully, but these errors were encountered: