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

fix(mini-indentscope): exclude special buftypes #546

Merged
merged 1 commit into from
Aug 30, 2023

Conversation

Subjective
Copy link
Contributor

📑 Description

Prevents indentscope from loading on special buftypes ("nofiles", "terminal", "quickfix", "prompt"), similar to indent blankline

ℹ Additional Information

None

@github-actions
Copy link

github-actions bot commented Aug 30, 2023

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

  • If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

  • If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

  • Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

  • README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

  • Proper usage of opts table rather than setting things up with the config function.

@Uzaaft Uzaaft changed the title chore(mini-indentscope): exclude special buftypes fix(mini-indentscope): exclude special buftypes Aug 30, 2023
@Uzaaft Uzaaft merged commit f4e981a into AstroNvim:main Aug 30, 2023
Uzaaft pushed a commit that referenced this pull request Sep 3, 2023
chore(mini-indentscope): exclude special buftypes
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.

2 participants