-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
watson config -e crashes if no config already exists #153
Comments
Thanks for the report @jbarnoud! Do not hesitate to submit a PR to fix this 😉 |
SpotlightKid
added a commit
to SpotlightKid/Watson
that referenced
this issue
Jun 16, 2017
fixes jazzband#153) Signed-off-by: Christopher Arndt <chris@chrisarndt.de>
Hi, the issue is still present for me (installed on windows powershell, release and dev version)
|
I sidestepped this by creating the C:\Users\xxx\AppData\Roaming\watson directory, and creating an empty config file before running the command. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When calling
watson config -e
to edit a configuration file, I get the following error message:If the config file already exists, then everything works as expected.
The behaviour I would expect when the config file does not exist would be that the editor is opened whith an empty file, and the config file is created if something is saved.
The text was updated successfully, but these errors were encountered: