-
Notifications
You must be signed in to change notification settings - Fork 394
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
Missing requirements after fresh installation of VS4Mac #2783
Comments
I am also seeing this. Looks like the fix for #2763 may have introduced a dependency on a Preview build of VsMac. The add-in is currently DOA from the gallery making this a high severity issue. As a workaround I was able to build and install from source, but that's not an option for most users. |
@wneessen Not your fault at all, I messed up when building the 2.8.0.1 extension last night. Sorry about this. I need to get better at making releases. I've been building the extension myself up until now, but I really need to start publishing the artifact from Azure pipelines. I just published 2.8.0.2 which fixes this. Thanks for reporting! |
Perfect. After the update and a restart of VS4Mac it works like a charme! Thanks for the quick response and the Extension :) |
Describe the bug
I just did a fresh installation of VS4Mac (8.4.5 b19). I opened the Extension Manager trying to install the VsVim extension from the Gallery. After the progress bar reaches the 100% is says: "Installation completed with warnings"
It tells me that I am missing some requirements, which I am not able to identify where to get them from. When I try to use the extension, it shows up in my Keybindings but it will not work. Once I restart VS4Mac, it will not show up in the Keybindings anymore but rather show "Custom".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Install the Extension and all requirements/dependencies are met or installed with the Extension.
Environment (please complete the following information):
Additional context
I am totally new to VS4Mac, so it might be totally my mistake and not a bug. If that's the case, I'd highly appreciate any hint to point me to the correct solution.
The text was updated successfully, but these errors were encountered: