Jonas Strittmatter

Everything should be good to merge now. Will wait for your feedback after you've had time to try it out though :)

> Other than that, the only thing missing is some way to map the mode names to vim language names in the cases where they don't match. Thanks for catching...

Just a note because you mentioned `filetype.vim`: you don't need to do something like mapping `.mmes` to `nroff-mode` (Nvim already detects .mmes files as nroff using `filetype.lua`).

Hey @IllustratedMan-code, I have decided to merge this feature in its current state. I'll wait for your (or the community's) contribution to add more mode -> filetype mappings.

That seems like a good snippet format to support in this plugin! Would you be interested in making a PR for the implementation? Also can you give an example of...

Thanks for your good explanation, that really helped me during the implementation! > These are defined when # type: command is in the header. I think trying to convert these...

Could you help me with the following: - can there only ever be one snippet per file? That would make the implementation simpler because I don't have to determine whether...

Change the snippet to the following: ```snippets snippet "([A-Z])#" "bb" Ar rv = '\\mathbb{' + m[1] + '}' endsnippet ``` Since you are using a regular expression as the trigger,...

I agree with @RaafatTurki that this seems like incorrect behavior. `type` and `ENUM.VALUE` are unrelated instances. The same problem can be observed using this example: ```lua local print = print...

Here is the output I get: ```json {"id":"cmpl-6QVU76IfN5u35VXfgoVK9y6CA81Zh","object":"text_completion","created":1671775575,"model":"code-davinci-002","choices":[{"text":" = False\ndevelopment = False\n\nimport","index":0,"logprobs":null,"finish_reason":"length"}],"usage":{"prompt_tokens":1,"completion_tokens":10,"total_tokens":11}} ```