Thank you for your reply. I'm not familiar with Sublime Text at all, so it took me a while to realize that "Package Control" is part of Sublime, not part of GitHub.
I "installed" neovim (though "install" is stretching things, since it's a standalone exe), apparently v0.2.3:
Build type: RelWithDebInfo
Then in Sublime I installed
Package Manager (I think via
Tools->Install Package Manager, though that option is no longer available since I installed it). Then I went to
Preferences->Package Settings->ActualVim Settings and it opened an editor buffer of apparently a file named "ActualVim.sublime-settings". But no matter what I do in that editor window I cannot change anything in it. I see where I think I'm supposed to edit the file:
I can click on that line and the cursor blinks where I clicked, but it will not let me edit it. No key does anything in that window. Also, now if I open any other file, it won't let me edit those either! So in a Windows command window I go to
C:\Users\minichm\AppData\Roaming\Sublime Text 3\Packages\ActualVim and search (grep recursively) for any file containing "neovim_path", and I find this file:
./Packages/ActualVim/settings.py. Using a different editor, I changed this line...
...then I re-open Sublime, and go to
Preferences->Package Settings->ActualVim Settings again, and again it opened an editor buffer of apparently a file named "ActualVim.sublime-settings". That line is still the same (it still says
"neovim_path": "",). And I still can't edit any file I load into Sublime; I can click anywhere and the cursor goes there, but no key I hit does anything.