L3MON4D3

Okay for postfix-style snippets where some part (most) of the trigger was probably already typed, the current solution doesn't make much sense, that's true. But there are other snippet where...

Naaaah, perhaps this should be put in the readme, you're not the first to be confused by this :D What might work is a hybrid of the two approaches: if...

In case you're not aware @p0da, luasnip already has [integration](https://github.com/L3MON4D3/LuaSnip/blob/master/DOC.md#select_choice) with `vim.ui.select` for changing choices. > I'm not really sure if integrating with cmp is possible as the sources just...

Nice, looking forward to it👍

I don't know much about packer's internals, does it change anything about the loaded plugins when PackerCompile is called? Your error "shouldn't" occur during normal usage I think.

@melkster Could you make sure you're adding snippets via `ls.add_snippets(ft, snippets)`? I didn't consider that not everybody is using that already (it is deprecated, but not yet unsupported).

I think they were hidden by design (and comfort, one less table to scan ;) ), I figured that autosnippets wouldn't be triggered via the completion-menu but, you know, automatically...

Sounds like something is messing with extmarks and moving them beyond the end of the line (hence 'end_row out of bounds'). I think that can happen if the line is...

Okay, I didn't experience your error with texlab (so far), but I did notice that, after updating compe (which I didn't do for some time), `ccls`-Snippet's extmarks get moved around...

Wow, weird... different nvim maybe? I'm on `NVIM v0.5.0-dev+1323-gd67dcaba0`. Apart from that, have you tried disabling all plugins except compe and luasnip?