L3MON4D3

Oh hey, much easier: use a `match_pattern` that accepts an empty string: ```lua postfix({ trig="vec", match_pattern = [[[%w%.%_%-%"%']*$]] }, {d(1, dynamic_postfix, {}, { user_args = {"\\vec{", "}"} })}, { condition...

> I'd like to make a snippet with an insert node that defaults to env.LS_SELECT_RAW when luasnip has a selection 'in store', or something else if not. Sorry, completely forgot...

> Tbh I'm still not sure what exactly your issue is I think @bew just thought that the condition-function is the only way to check whether there is a selection

> note: I actually noticed that using has_selected_text from the extra show conditions module always returns false when inside a snippet for some reason. Oh, I'll check that out >...

Oh yeah, for sure! As far as I understand, this would basically be whatever is in `DOC.md`, but as emmylua-annotation, so lua-language-server can parse it? If so, I'd say there...

Only that it's marked as draft, and adding annotations for a small number of api-functions only seemed a bit weird. But you're right, better that than nothing. I'll look into...

> Sounds good. I think that splitting the work into smaller PRs will be less overwhelming than documenting the entire API at once Ah, yeah, probably also true :D >...

Hey all, sorry for the long silence 😅 > There's still a big question on the duplication of documentation between the vim help page, the DOC.md file and soon in...

I've looked into this a bit, and I think we can just extract the necessary information using `lua-language-server`. It has a feature where it exports all types in a codebase,...

Yeah, that's what I'm thinking of :D We'd have some kind of marker in a (not yet existing) `DOC.md.template`-file, and that marker contains a type and a function-name, which we...