Skip to content
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

Mark eglot completions as non-exclusive #770

Merged
merged 1 commit into from Dec 15, 2021
Merged

Mark eglot completions as non-exclusive #770

merged 1 commit into from Dec 15, 2021

Conversation

gmbuell
Copy link
Contributor

@gmbuell gmbuell commented Dec 14, 2021

Add a property to the eglot-completion-at-point results marking it as non-exclusive. This will allow completion to fall back to other less precise completion backends if eglot returns no results (e.g. dabbrev)

@joaotavora
Copy link
Owner

Hello. This is interesting. Do you know reads this property, how it works? Can you point me to some documentation?

@gmbuell
Copy link
Contributor Author

gmbuell commented Dec 15, 2021

minibuffer.el :exclusive code

Discovered this while trying to stop using company-mode. It seems to work correctly but could be incredibly specific to my configuration. I use consult-completion-in-region as my completion-in-region-function. My only two completion-at-point-functions are eglot-completion-at-point and cape-dabbrev to turn dabbrev into a capf.

@joaotavora
Copy link
Owner

Alright, I didn't know about that option, and it looks like a fine idea if indeed it does help you. Can you format the commit message like most others (80 chars, etc), and tell me if you have a FSF copyright assignment? (your simple patch can go in regardless). This will help me press the big green button.

Add a property to the eglot-completion-at-point results marking it as
non-exclusive. This will allow completion to fall back to other less precise
completion backends if eglot returns no results (e.g. dabbrev).
@gmbuell
Copy link
Contributor Author

gmbuell commented Dec 15, 2021

Fixed the commit message line length. No FSF copyright assignment.

@joaotavora joaotavora merged commit 670ee61 into joaotavora:master Dec 15, 2021
@joaotavora
Copy link
Owner

Thanks! You should get a FSF copyright assignment if you plan on contributing more to Eglot and or Emacs.

@gmbuell gmbuell deleted the patch-1 branch December 15, 2021 21:54
bhankas pushed a commit to bhankas/emacs that referenced this pull request Sep 18, 2022
…exclusive"

Add :exclusive 'no to eglot-completion-at-point results marking it as
non-exclusive. This will allow completion to fall back to other less precise
completion backends (e.g. dabbrev) if Eglot's returns no results.

* eglot.el (eglot-completion-at-point): Set :exclusive to 'no

Copyright-paperwork-exempt: Yes
bhankas pushed a commit to bhankas/emacs that referenced this pull request Sep 19, 2022
…exclusive"

Add :exclusive 'no to eglot-completion-at-point results marking it as
non-exclusive. This will allow completion to fall back to other less precise
completion backends (e.g. dabbrev) if Eglot's returns no results.

* eglot.el (eglot-completion-at-point): Set :exclusive to 'no

Copyright-paperwork-exempt: Yes
bhankas pushed a commit to bhankas/emacs that referenced this pull request Sep 19, 2022
Add :exclusive 'no to eglot-completion-at-point results marking it as
non-exclusive. This will allow completion to fall back to other less precise
completion backends (e.g. dabbrev) if Eglot's returns no results.

* eglot.el (eglot-completion-at-point): Set :exclusive to 'no

Copyright-paperwork-exempt: Yes
#770: joaotavora/eglot#770
jollaitbot pushed a commit to sailfishos-mirror/emacs that referenced this pull request Oct 12, 2022
Add :exclusive 'no to eglot-completion-at-point results marking it as
non-exclusive. This will allow completion to fall back to other less precise
completion backends (e.g. dabbrev) if Eglot's returns no results.

* eglot.el (eglot-completion-at-point): Set :exclusive to 'no

Copyright-paperwork-exempt: Yes
GitHub-reference: close joaotavora/eglot#770
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants