Christian Clason

I don't see how completion is related to type-checking?

Can you give a _concrete_ example how this would look in practice? What sort of "types" should be recognized?

Right, that's something different. I can see that being useful to some but quite niche in general, so I'm not convinced the cost-benefit ratio is in favor of it. But...

Well, _somebody_ has to implement (and then maintain) it -- especially adding this information for the (many, many) "common packages".

Julia does, for one (as well as some numbers and punctuation marks). Here's the full list of double-struck (or "blackboard-bold") letters the internal REPL supports for auto-replacement: ``` \bbA \bbH...

Here's a picture of all of them from within vim (using Fira Code Retina, with apparently a fallback font for the missing ones -- note that the Fira Code versions...

I think earlier comments just referred to the (one-time) appimages linked in the original post. Note that this PR was closed, not merged. We currently indeed (can)not provide aach64 appimages.

All very understandable. I think there is (always) interest in improving the build CI workflow; the issue is more that not enough people on the current team are familiar enough...

I believe interest in using Docker to build releases has just increased somewhat since Github deprecated the Ubuntu-18.04 images so we had to switch to 20.04, which dropped support for...

I believe the gold standard is https://github.com/nvim-lua/plenary.nvim#plenaryasync, but @lewis6991 [rolled his own for GitSigns](https://github.com/lewis6991/gitsigns.nvim/pull/479). Either could conceivably be upstreamed if deemed useful enough.