-
Notifications
You must be signed in to change notification settings - Fork 49
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
Error when vim files are in a path with spaces #89
Comments
Gasp, I think the test suite tests that staged file with space are well handled, but I don't think I test repository path with white spaces... I'll give it a look, thanks. |
Note this isn't about the repository path having spaces it's vim's configuration files being in a location with spaces in it. In this case Vimagit errors out when opening vim.
|
I misread it. Thanks for the tip. |
Arh, it's been such a pain to reproduce your setup! Spaces should be forbidden, everywhere! :) Could you try the branch next, and let me know if it fixes your problem? Thanks for the issue. |
Yeah it was a terrible choice by Dropbox to not only include spaces but brackets as well. I'll give it a try when I have a moment. Might not be until the weekend. |
No problem, you waited 3 months, I can wait too :) |
Could you confirm it has fixed your problem before I merge it into master. |
It gets further (vim loads without error) but doesn't look like it's entirely fixed:
This happened when running |
I believe this is now fixed in banch next. All tests in integration are done with the tested repository path containing spaces. Last flow in integration is that vimagit path does not contain space. Thanks for your feedback! |
Yep working now 👍 Thanks.
|
I store my vim files in Dropbox. The path has spaces and brackets in it (Note that the
Dropbox (Personal)
bit wasn't my choice. When you add a Dropbox for business account they rename the Dropbox folder to this and add aDropbox (Business)
one). Whilst everything else works with this arrangement, vimagit does not:The text was updated successfully, but these errors were encountered: