-
-
Notifications
You must be signed in to change notification settings - Fork 524
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
Editor can't be launched on Windows when using full path to editor executable #1096
Comments
Update: it worked when I copied and pasted the Vim.exe file in my %windir%\system32\ folder and then changed the value of the 'editor' key to "Vim" |
Thanks for the post and the update. I think you have found a Windows compatibility bug in jrnl. I'm trying to reproduce this, and the editor key works for me when the exe is in the path (just like it does for you), but not when I spell out the whole path. The problem appears to be that it's transforming backslashes into two backslashes. My editor key:
My error message:
I'll see about getting a fix for this in our next release. |
for me, I switched to single quotes with the doubled backslashes and this resolves the problem |
This was fixed by #1153. |
Support Request
Environment
Jrnl
--diagnostic
output:jrnl: v2.5
Python: 3.8.6 (tags/v3.8.6:db45529, Sep 23 2020, 15:52:53) [MSC v.1927 64 bit (AMD64)]
OS: Windows 10
Install method: <!-- How did you install jrnl?
pipx
What are you trying to do?
I am trying to change my editor to vim.
What have you tried?
I changed the value of the "editor" key on the yaml file to "vim", "gvim", "Vim", "C:\tools\vim\vim82\vim.exe" - none of them worked.
Then I tried to follow the instructions on the "recipes" page on the documentation and tried to set it to notepad++, just to see if it would work. It didn't work, either. (The path to my notepad++ executable is right)
Then I tried with a bunch of other text editors - the only one which worked was notepad.
Other Information
If applicable, please run jrnl with --debug and paste the output.
(The editor here is still set to notepad++, hence the error)
The text was updated successfully, but these errors were encountered: