Modify completion-at-point-functions locally and don't override. #665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This simple modification only changes
completion-at-point-functions
locally, and it adds#'lispy-clojure-complete-at-point
to it, instead of overiding the var.Since it's only evaluated after
cider-mode
, we can count thatcider-complete-at-point
is already in the capf.And adding the lispy function in that way, it makes it play better with other packages that locally binds
completion-at-point-functions
, like eglot.The same idea is used by CIDER