Closed oiiiiiiii closed 1 month ago
Found a workaround by adding
Could it be that you wanted to map it in visual mode instead of select mode? Did you use xmap
or smap
or the much broader vmap
? The expectation of a user in select mode (which is not visual mode) is that typing overwrites, so most select mode mapping that map to typable characters are done in error.
This is a common mistake, explained (maybe poorly) in https://github.com/SirVer/ultisnips/blob/master/doc/UltiSnips.txt#L381. If you indeed want something mapped in select mode to tab, then setting the UltiSnipsMappingsToIgnore
No I really meant the select mode, not visual mode. My problem was that I wanted to map
When I bind something to tab in select mode, I can only trigger that bind when there are no tabstops generated by snippets.
Expected behavior:
I can bind tab the way I like when I don't even use it for UltiSnips
Actual behavior:
I can not.
Steps to reproduce
Context: The select mode is also being used for default placeholders (which is where I would like to have my own binding to tab) but this behavior also occurs in snippets that don't use that and when I manually select something as described in the reproduction steps.
If there are no active snippets, it works perfectly fine when I select something and trigger my custom map.