Skip to content

Commit 0e6046a

Browse files
committed
feat(ai): add link to AstroCommunity AI entry
1 parent caf4be6 commit 0e6046a

File tree

1 file changed

+13
-0
lines changed
  • src/content/docs/recipes

1 file changed

+13
-0
lines changed

src/content/docs/recipes/ai.mdx

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,19 @@ title: AI Completion
55

66
There are many AI plugins out there which provide completion through various mechanisms. This page goes over how to build onto an AstroNvim configuration in order to easily hook up and configure different AI completion plugins.
77

8+
:::tip
9+
10+
This is available in the [AstroCommunity](https://github.com/AstroNvim/astrocommunity/tree/main/lua/astrocommunity/recipes/ai) and the AI completion plugins within AstroCommunity utilize the configuration it sets up.
11+
12+
```lua title="lua/community.lua" ins={3}
13+
return {
14+
"AstroNvim/astrocommunity",
15+
{ import = "astrocommunity.recipes.ai" },
16+
}
17+
```
18+
19+
:::
20+
821
### Completion Engine Integration
922

1023
In order to make AI plugins play nicely with AstroNvim it's important to set up an integration point with completion engines in Neovim in order to accept AI recommended code. Depending on which completion plugin you are using, you may need to modify the configuration of the mappings to account for interacting with normal completion as well as AI recommended code. By default AstroNvim utilizes a "super-tab" like configuration where the `<Tab>` key is used for triggering completion, navigating through snippets, and navigating through completion items. These code snippets change this configuration so that the `<Tab>` key is only used for snippet navigation and AI completion. To navigate through the completion lists, it would then be recommended to use `<C-n>` and `<C-p>`.

0 commit comments

Comments
 (0)