-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Support company-mode #490
Support company-mode #490
Conversation
(lambda (_buffer err) (message err)) | ||
nil)) | ||
(defun cider--jump-to-def-eval-fn-1 (response) | ||
"Handle the synchronous response." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
response -> RESPONSE
Overall the code looks good to me. I guess using |
And use it in `cider-complete-at-point'.
It's a hack, but a simple one.
Updated, rebased and pushed. Making By the way, when the cider middleware is used, the same error makes it spew a stack trace in a hidden buffer in background and apparently not respond to the request at all (Emacs waits indefinitely). |
You might also report it here https://github.com/clojure-emacs/cider-nrepl, so we won't forget about it. |
Ah, I think it's clojure-emacs/cider-nrepl#7. |
Continued from clojure-emacs/ac-nrepl#30.
So far the only bug I'm aware of is in
cider-company-location
: ifcider-jump-to-def
fails with namespace error, the handler just prints the error message withmessage
, and the former function returns the current buffer. Shouldnrepl-make-response-handler
useerror
in these situations?Also note that it works differently from what @steckerhalter did in
company-cider
: instead of showing the output ofclojure.repl/source
, it actually opens the file where a given function is defined.