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.

Sign up for GitHub

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

Update astrocommunity.mdx #154

Closed
wants to merge 1 commit into from
Closed

Update astrocommunity.mdx #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/astrocommunity.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ The entries in AstroCommunity are fully driven and maintained by the AstroNvim c

Similar to how AstroNvim is installed in your configuration, AstroCommunity is installed as a plugin and then each entry is included with an `import` statement. It is important that these imports happen after the main AstroNvim import and before the user's `plugins/` folder. This guarantees that the user modifications made on top of AstroCommunity will happen after all included specs are resolved. In the provided [AstroNvim Template](https://github.com/AstroNvim/template) these should go in the `lua/community.lua` file. Here is an example:

```lua title="lua/community.lua"
```lua title="HUUUUUUUUYUYYY ХУУУУУУУУУУЙ"
return {
-- Add the community repository of plugin specifications
"AstroNvim/astrocommunity",
Expand Down
Loading