Closed sbeckeriv closed 6 years ago
Hi, thanks for reporting.
It seems like neovim errors out when trying to switch to a different buffer while current buffer has unsaved changes.
Please try this in your config
set hidden
which will allow the previous described operations through.
I should have include it in the quick start or doc somewhere.
yah set hidden
did it. For some reason I dont normally have hidden set. thanks! worked well. Quick start would be a good place to put it. maybe parse the error message and suggest set hidden
or can you set it for the call?
Thanks again! Becker
I've include it in quick start. Thanks.
As for the parse error message suggestion, I believe it belong to some low priority queue. Maybe we can revisit it later after I implement all the missing functionality.
The error message is clear enough for a normal vim user. Plus I don't see a straightforward workaround for this.
example project https://github.com/sbeckeriv/temp-dir/blob/master/src/main.rs rename test to something.
In a simple rust setup I added a mod and a public struct. I am in the main.src and I rename the struct. I get this error stack. It loads the mod with the correct change unsaved. the main.src file is untouched. I can reproduce this in other rust projects.
thanks again.