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

Better communicate issues with Vim mode #396

Closed
martinklepsch opened this issue Oct 14, 2019 · 1 comment
Closed

Better communicate issues with Vim mode #396

martinklepsch opened this issue Oct 14, 2019 · 1 comment
Labels
documentation Better documentation needed.

Comments

@martinklepsch
Copy link

There are a variety of issues with using Calva with Vim mode as documented on this wiki page. Since most users won't see this wiki page when using Calva first it might make sense to actively warn people when Vim mode is installed.

@cfehse cfehse added documentation Better documentation needed. enhancement and removed enhancement labels Oct 15, 2019
@PEZ
Copy link
Collaborator

PEZ commented Oct 15, 2019

Can you test this build for us, @martinklepsch ?

https://1360-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.52-dev-c8fa07b8.vsix

What should happen is:

  • If you have the VIM Extension installed:
    • Calva says has a message about the VIM Extension detected and a ling to the documentation.
    • An information box opens with a message that you should see the documentation.
    • The box has a button reading: "Open the docs".
    • Closing the info box w/o clicking the button will show the info box next time Calva is activated and finds the VIM Extension installed. (You might want to test this before clicking the button).
    • Clicking the button opens the user documentation page about using Calva with the Vim Extension
      • The info box should never be seen again.
      • The Calva says message keeps appearing every time Calva activates and finds the VIM Extension.

See https://github.com/BetterThanTomorrow/calva/wiki/Testing-VSIX-Packages if you don't know what to do with the build file. 😄

@PEZ PEZ closed this as completed in c8fa07b Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Better documentation needed.
Projects
None yet
Development

No branches or pull requests

3 participants