daily neovi(de)
This is not exactly nvim specific but is definitely related. I've started using Neovide in Windows to help it behave a bit better as a Sublime Text replacement. Part of the niceness that Sublime had was integration with Windows Explorer, being able to double click or drag files into a new window on whatever desktop.
Unfortunately, I created a bit of additional complexity for myself by using the WSL version of Nvim as the server for Neovide. This is much neater conceptually since I only have one configuration but has a small catch: you need to run Neovide with the `--wsl` argument for it to work.
It was no issue updating the shortcut in
to add the argument since shortcuts have that functionality built in. The tricky part was getting my right-click context menu working in explorer.
I haven't directly played around with the shell menu before, so this was a bit of an adventure. Turns out it's all driven by registry values, which immediately raises alarm bells with me. Any time I've had to dig around in there has been unpleasant at best.
After some searching around, I found these keys:
These contained the value:
This seemed easy enough to adjust but turn out to have some mild complexities:
Not entirely sure how the quotes are supposed to function and I don't know if I care to find out. Luckily the path had no spaces in it, otherwise I may have been in trouble.
This worked for directories but was still failing to work when opening a file directly. I assumed this was due to more registry keys that I hadn't managed to locate (the regedit search function is horribly slow).
Luckily while poking around looking for alternative solutions, I found a file in the neovide install directory: install-context.reg
This was the solution to all my problems and ensured I could repeat this process in the future in a much simpler way. It was simply a registry script for adding all the keys for the context menu. A quick edit of the values in the file, for example:
Run the script, and now everything functions as expected.
I suppose the next step is to get regular double-click file opening working, but I fear that will be another, much scarier journey.
---