Closed zacps closed 5 years ago
Is there a simple way to reproduce the issue?
Create a file in vim, save. While vim is running open another instance of vim and use ctrlp to open the file. Choose diff.
On 23 Aug 2016 6:54 a.m., "Christian Brabandt" notifications@github.com wrote:
Is there a simple way to reproduce the issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/chrisbra/Recover.vim/issues/40#issuecomment-241513246, or mute the thread https://github.com/notifications/unsubscribe-auth/AJX1cHp6c7qmoig5VgQ-vdaGfMNlPzhIks5qifB5gaJpZM4JjpWM .
can you show the message please?
Sorry for the delay
Hm, you second message shows the usual [D]iff prompt?
The first screen happens some of the time, some error in ctrl-p (I'm not sure if related but I haven't seen it happen without this plugin.) The other two are what happens most of the time, the third one is what happens if you d(i)ff. Enter just opens the file and it'll warn again about a swap file on write as usual.
Has anything happened here? I have the same problem with fzf. Any information that could be useful?
Please create an step by step reproduction. Then I can have a look
Am 21.11.2018 um 09:33 schrieb Christian Rapp notifications@github.com:
Has anything happened here? I have the same problem with fzf. Any information that could be useful?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I think, those plugins may need a nested
somewhere in the call of their auto commands. I don't think it is a problem of my plugin. So closing.
The swap file found message comes up without the options at the bottom then it asks you to press enter to continue which just opens the file. Is it possible to fix this?