IAmIlliest

I'm seeing the same issue. Both when running nvim inside Windows Terminal or Neovim-qt as admin. Neovim details below. Let me know if there is a way to get you...

No worries, give me a day or two in order to get python and friends setup, and then test it....software developer skills; I have not :-)

Sorry for the verbosity of this post, just trying to give you some extra context in case you notice any confounding factors that might invalidate the results. ### System Context...

So, I have no idea what I'm doing, but can open things in vim....so....you've been warned :-) I'm guessing the above is to do with use of the MSCV toolchain...

Is this an old version of hererocks / lua by any chance? I'm just getting the impression that it's using an old version that is lacking Windows support....but I also...

Hmmm, just noticed the 5.1.5 binary for the interpreter that I downloaded is **lua5.1.dll** not **lua51.dll** Not sure if that's a typo somewhere in the source, or if I have...

Glad it's of some use! No I haven't tried gcc as yet, just been giving myself a crash course in Visual Studio Code to try and work out how to...

I'm seeing the same problem as the OP. It is occurring on Windows 10 Pro: Version 10.0.19042 Build 19042 Version 20H2 (OS Build 19042.985) I'm using Windows Terminal: Version: 1.7.1033.0...

Just dropping in to say I have this same issue quite often. It frequently then seems to cascade, ending up at the point where the debugger can't even attach to...

Yep, confirming the same symptoms as Leo above. Probably unrelated, but just in case it isn't, I'm using Conda environments. For what it's worth, I'm doing the bits below in...