dcampos

> First of all, thanks! Great plugin! Thanks! > Would it be possible to enable the plugin to support mixed vim functions and static texts in the placeholder choices? I...

Hi, thanks for the question. No, currently there's no way to do that, regardless of which mode you expand the snippet from. If there is a `$0` tab stop, the...

While working on this, it could be a good idea to change other API methods as well. The `snippy.next()` and `snippy.previous()` mappings are short and easy to type, but also...

Hi. That kind of reference to another snippet from a snippet's body isn't possible, though I agree it would be handy sometimes. I'm not aware of any snippet engine that...

> The snippets engine I used before, vim-vsnip, supports that: https://github.com/hrsh7th/vim-vsnip#features - it calls that feature "nested snippet expansion". Interesting. I thought the "nested snippet expansion" referred to expanding a...

Hi, > Is snippy expected to fill empty tab stops with placeholder text? Using lua-language-server, most of the snippets already have placeholder text at the tab stops, but the `function...

Hey! Please let me know if I'm missing anything, but pressing `` generally doesn't finish snippet expansion; it enters normal mode and, if you don't have a normal mode mapping...

I've decided not to make the additional changes to the API.

There is now the `SnippyFinished` autocmd. The user can set up it like this to enter normal mode after ending the snippet: ```vim autocmd User SnippyFinished call feedkeys("\", 'n') ```

Hey! Sorry for the late response. I'm afraid I'm unable to reproduce the issue. I created a `plaintex.snippets` file containing the following snippets: ```vim-snippet snippet begin Just begin. snippet \begin...