-
Notifications
You must be signed in to change notification settings - Fork 73
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
z command breaks with gvim #148
Comments
@blackgeorge-boom this looks like an issue with configuration, as Vimwiki syntax is used instead of Markdown. Isn't it possible that you use a different configuration in Vim and Gvim? Does the following command list the same directories?
|
@michal-h21 Currently, the issue is gone (and the output of your command lists the same directories for both). I'll wait a bit (because strangely the issue appears randomly) and try your command again. Otherwise, I'll close the issue. Thank you for your help! |
@blackgeorge-boom hope it will not start again, because it seems quite mysterious :) |
@michal-h21 It came back :). I can indeed confirm that the output of
is the same nevertheless. I also noticed that now when I use EDIT: Saving everything, closing, and re-opening seems to fix this. I'll try to see if this related to a remnant swap file, in case gvim is closed abruptly. Would you have any other debug suggestions? |
What should Anyway, I would try to create a minimal |
Ah, this is from the
|
Hmm I see, I will try that, thank you! |
Ah, I totally forgot about this command! I guess that I've added that on a feature request, because I don't use it myself. |
In
gvim
, when I use thez
command, the new vimwiki file is not created properly.For example, using
z
over the wordtemp
in one file, creates a new file with header:whereas, the correct would be:
More often than not it works, but sometimes it stops working and produces the above result.
In
vim
, this seems to be working fine (although there were random times that this would break as well).I'm not sure how to debug this, hence opening this issue. I'm using
gvim
8.1.2269 and Ubuntu 20.By the way, thanks for the awesome plugin! Been using it for a few years now. I recently switched to
gvim
to allow for more cute fonts ;).The text was updated successfully, but these errors were encountered: