-
Notifications
You must be signed in to change notification settings - Fork 344
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
Auto-completion doesn't work right in new build #787
Comments
Oh, that's very sad. Do you have some special package for haskell-mode or just plain |
I checked the haskell-completions.el file, and nothing seems to be wrong when I invoke its functions in Emacs when in Haskell mode. As this is the file which you had changes merge into, I don't think the problem is there. |
I've had this happen with company-mode. I haven't been able to make it happen consistently. I'll take a screenshot next time it does. |
I don't use company-mode or any other auto completion modes. Here is what I get by typing some import expressions after λ> and pressing tab:
It looks like part of the string is repeated. I would expect the following behavior: Expected 1) Pressing tab after "import Co" shouldn't change it. It looks like this issue might be related to removal of the unused string (h1) from completions (cs) in haskell-process-get-repl-completions function of haskell-process.el (related commit: f0466a2). Adding the unused string (h1) to the completion list (cs) solves this issue for me. But I am not sure if this change breaks something else instead. (let ((cnt1 (match-string 1 h0))
(h1 (haskell-string-literal-decode (match-string 3 h0))))
(unless (= (string-to-number cnt1) (length cs))
(error "Lengths inconsistent in `:complete' reponse"))
(cons h1 cs))) |
This seems to be fixed by #810. |
I just got the new version of haskell-mode. The auto-complete function does not seem to work now.
Say one wants to write "sequence" and has written "sequ". Auto-completion now yields "sequsequence" instead of "sequence".
The text was updated successfully, but these errors were encountered: