You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run FVim.exe --wsl, FVim starts up just fine, but running just FVim.exe without the --wsl option gives an error (I believe because neovim is not installed on Windows.)
Therefore, if I simply set FVim as my default editor for .txt files in Windows, it produces an error when trying to open the .txt file because Open with... can't provide the --wsl option.
I tried using a .bat script to launch FVim with the --wsl option, and it does work, but it also spawns a cmd window, which is less than desirable.
I can use a .vbs script to run the .bat script, and that can hide the cmd window, but Windows won't allow you to select a .vbs script as the default editor for a file type.
Could we have a config file that defines the default options used when FVim is run without options? For a user like me whose nvim is installed in WSL, I will never want to run FVim without the --wsl option, so it would make sense.
The text was updated successfully, but these errors were encountered:
I'm running neovim in WSL2.
If I run FVim.exe --wsl, FVim starts up just fine, but running just FVim.exe without the --wsl option gives an error (I believe because neovim is not installed on Windows.)
Therefore, if I simply set FVim as my default editor for .txt files in Windows, it produces an error when trying to open the .txt file because Open with... can't provide the --wsl option.
I tried using a .bat script to launch FVim with the --wsl option, and it does work, but it also spawns a cmd window, which is less than desirable.
I can use a .vbs script to run the .bat script, and that can hide the cmd window, but Windows won't allow you to select a .vbs script as the default editor for a file type.
Could we have a config file that defines the default options used when FVim is run without options? For a user like me whose nvim is installed in WSL, I will never want to run FVim without the --wsl option, so it would make sense.
The text was updated successfully, but these errors were encountered: