gptel-backend #41
Draft
gptel-backend #41
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is all generated code that has been lightly tested. It likely has lots of issues and needs to be able to do more. But for now I will be using this while I develop and improve it as I find issues. Why this instead of emacs-cody? Personally I prefer chat over autocomplete. gptel provides fantastic hooks all over emacs for chatting. I also see this as a useful backend to include our smart context in the future.
It needs to use the key argument as a default. This is a bug in upstream I need to fix, since it ends up only using the key for the default gptel-backend.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is all generated code that has been lightly tested. It likely has lots of issues and needs to be able to do more. But for now I will be using this while I develop and improve it as I find issues.
Why this instead of emacs-cody? Personally I prefer chat over autocomplete. gptel provides fantastic hooks all over emacs for chatting. I also see this as a useful backend to include our smart context in the future.