carried-away

So I figured out the issue, kind of. At first, I was manually running mkdocs build in my normal windows environment, the match_path: my-news/posts/.* did not match anything. However, running...

I apologize for opening this issue. I installed your amazing plugin in a different environment and found that it worked without issue. The environment I initially ran into a problem...

> This is my current workaround: > > ```lua > use({ > 'kdheepak/lazygit.nvim', > requires = { > 'nvim-lua/plenary.nvim', > }, > config = function() > if SystemOS == "Windows"...

I just tried to debug with lazygit --debug, strangely enough when using the --debug flag, the normal colors appear 

> [@fdev31](https://github.com/fdev31) Codesnap.nvim v2.0.0-beta.17 has been released. Could you test whether everything works correctly on beta 17? This version introduces some breaking changes, so it's best to completely uninstall your...

If I was good enough, I would certainly do a PR. but I'll put a $50 bounty on this if anyone is interested.

> you are not calling it in the correct position/state it seems I was thinking about this. Wondering if it's just an issue w/ vs code loaded snippets. Here is...

There must be something else going on because I'm still getting the same error. I'm using your example 1:1 ``` lua vim.keymap.set( { "i", "s" }, "", require "luasnip.extras.select_choice", {...