Carlo Baldassi

What's the reason/use case for this?

It's a nice feature to have but not entirely straightforward to implement. I'll keep it in my todo list (and will accept pull requests if someone volunteers to do it...

This is fixed on latest master. Until I release a new version (hopefully soon) you can `Pkg.checkout("ArgParse")`.

I see. After a short investigation, this seems like a Julia bug (still present in 0.7), whereby printing anything to stdout/stderr while the parsing is proceeding is causing all sorts...

this is the culprit: https://github.com/JuliaLang/julia/issues/27168

Do you have the latest version of the plugin? Can you provide some details about your configuration? I cannot reproduce this behavior, for me it works fine.

I just pushed a commit that might help, at least a little. Could you test it? That file is quite demanding... the main problem seems to be in the abundance...

@ronisbr I have a branch in #254 that might still help a little bit. It certainly doesn't solve the issue. I tried a few tricks but I'm out of ideas....

Ok thanks. I have now checked this file with an older version of vim and noticed that this is very, very similar to #131: the problem is much more severe...

It would be very helpful to know exactly: * your configuration (e.g., did you use the mapping suggested in the coc.nvim README? did you change any of the options for...