Replies: 1 comment 2 replies
-
Principally because it's not as productive. If I understand you correctly:
Or;
I understand you linking the use of the word "command" to Neovim Commands, however Slash Commands were designed to mimic the functionality in Zed.
Please do share the "NVIM" way of doing things |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
Thanks for the cool plugin. Having a lot of fun playing around with it.
Writing my issue about slash command completion (#587) got me thinking - are slash commands the most "NVIM" way of handling that functionality?
NVIM already has a fully-featured command infrastructure (
:
) - why not leverage that instead of slash commands? It seems that by (ab-?)using autocompletion to re-implement commands will always see you fighting many edge-case bugs.It should be possible to simply register all slash commands as buffer-local nvim commands. It may need some prefix/suffix to avoid a collision, but I would not mind typing something like
:CCBuffer
.This would also make it easier to add keybinds for these.
These "normal" commands could probably co-exist with slash commands just fine.
Just food for thought. This is not a 100% baked idea :)
Beta Was this translation helpful? Give feedback.
All reactions