Re: [vim/vim] Add option to disable q: (Issue #21110)
yousefx0 (Vim Github Repository) <[email protected]>
| Newsgroups | gmane.editors.vim.devel |
|---|---|
| Message-ID | <vim/vim/issues/21110/[email protected]> |
yousefx0 left a comment (vim/vim#21110) Thanks a lot for the response, appreciate you taking the time. Just to clarify though, because I don't think I explained myself that well the first time this isn't really about vim guessing what I meant, I actually agree with that philosophy. The issue is that `autocmd CmdwinEnter : quit` doesn't really behave as if `q:` was never triggered in the first place, the window still shows up for a split second before it closes, so its more of a "hide it fast" than an actual "don't open it". You can notice this flicker pretty easily and it appears quite often. My ohter consideration was `<nowait>` but it doesn't fix this either since this isn't a mapping vs mapping conflict, its a mapping vs built in command one. So basically right now there's no actual clean way to get rid of this, either you get the flicker or you get the delay, one or the other. What I'm getting at is, q already knows how to instantly prioritize stopping a macro recording over waiting for more of the built in `q:`/`q/`/`q?` sequence, so what if that same kind of priority applied to user mappings (as a settable option or something) too? That way people who already remap it (which again, from what I've seen, quite a lot do, **especially** the `q:` one) wouldn't have to deal with the delay, and `q:`'s default behavior wouldn't have to change at all for anyone who doesn't touch it. I think this kind of fix might be worth considering. It feels less like "messing with built in stuff" and more like fixing a gap in how q disambiguates against user maps. -- Reply to this email directly or view it on GitHub: https://github.com/vim/vim/issues/21110#issuecomment-5372982451 You are receiving this because you are subscribed to this thread. Message ID: <vim/vim/issues/21110/[email protected]> -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/21110/5372982451%40github.com.