Grzegorz Rozdzialik

Hey @mbest, thanks for reporting this 👍 It seems like a valid use case to be able to allow this. However, I'd like to make the rule more lenient by...

Oh, right, I forgot to mention that workaround :smile: Good catch Thanks for mentioning it :+1:

Thanks for introducing more updates :+1: > It is an invalid usage of hooks but it doesn't trigger any rules, because current rules rely only on, at most, two levels...

At the time of writing, I am using the following `coc-settings.json` to get ESLint to work: ```json { "eslint.probe": [ "javascript", "javascriptreact", "typescript", "typescriptreact", "html", "vue", "markdown", "svelte" ], "eslint.options":...

Thanks! It does look better now: 

I'm dubious whether this is the problem with the `complete` option of user commands. I thought the issue is in the code parsing the current cmdline and incorrectly assuming there...

Interesting, thanks for sharing these details. Why did it work for the first argument, though? I get correct completions for the first argument of `DiffviewOpen` and I guess these completions...

Yup, I confirm I can see the correct completion candidates in the `xs` list in the fuzzy filter. ```vim function FuzzyFilter(ctx, xs, c) echomsg "ctx" a:ctx echomsg "xs" a:xs return...

@gelguy Is there any way I can help out more here? Should I try to adjust the `cmdline` parsing logic so it only takes one argument into account instead of...

That sounds great! Take your time, there's no rush, and it's just an inconvenience, not a showstopper.