-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
feat(editing-support): add cutlass-nvim #174
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new list_insert_unique
syntax
lua/astrocommunity/editing-support/cutlass-nvim/cutlass-nvim.lua
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gotta get them style points 👀
Co-authored-by: Micah Halter <micah@mehalter.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@owittek, is it working for you? Cutlass only works for me if I set |
Yep it works for me. I've set the "User AstroFile" event to load the plugin which triggers as soon as you enter a buffer. |
Maybe it's because I use |
@owittek it doesn't work for me. The |
I found the culprit: which-key. Disabling it makes cutlass work again. |
I think I fixed it by adding {
"folke/which-key.nvim",
opts = function(_, opts)
opts.triggers_blacklist = {
-- list of mode / prefixes that should never be hooked by WhichKey
-- this is mostly relevant for keymaps that start with a native binding
i = { "j", "k", "d", "D", "s", "S" },
v = { "j", "k", "d", "D", "s", "S", " ", "g" },
n = { "d", "D", "s", "S", "m" },
}
return opts
end,
}, to However, there are still warnings from
|
No description provided.