Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When opening as default editor, can't use --wsl #246

Open
schaefsteven opened this issue Jan 9, 2023 · 1 comment
Open

When opening as default editor, can't use --wsl #246

schaefsteven opened this issue Jan 9, 2023 · 1 comment

Comments

@schaefsteven
Copy link

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.

@yatli
Copy link
Owner

yatli commented Apr 3, 2023

Hi,

If you're interested in hacking this, here's the FVim config code: https://github.com/yatli/fvim/blob/master/config.fs

It will be picked up before firing up nvim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants