hinell

Yeah, currently it's a bit inconveniet to do that: we have to run a pre-configured command. This isn't good. We have to modify `find_files` picker.

It's fine if you list all features at once but there might be many though.

@mklcp Well, it fails in bash 5.2.15 but it doesn't fail in zsh. Sadly, this grammar parser is used for both in many places, which is not correct!

@amaanq Yeah, I know, but it's used by VS Code sadly lol.

@amaanq Nice, but I think it's better to map its native parser to tree-sitter api than writing entire grammar cause this way you will be in sync with original codebase....

@clason Is there specific neovim policy on features removal? Recently, I've wasted 3 hours fixing ` lsp.get_active_clients()` calls in my [lsp-timeout.nvim plugin](https://github.com/hinell/lsp-timeout.nvim).. Just want to ensure that my plugin setup...

> Also, why did you fix these calls? Backwards compatibility. Some package registries still ship old nvim. I'm using nightly version though, but anyway... Checkout my plugin btw, you will...

Any progress on this? I also request to support the `scope` field: ```json "help": { "description": "These are snippets common to TypeScript and JavaScript and ECMA Scripts", "prefix": "help", "scope":...

https://github.com/L3MON4D3/LuaSnip/pull/846

@domenic Yup, I can cofirm that.