Tobias Diez

I did a bit of research how other (code) editors are handling this and was a bit surprised that vscode for example uses a simple write (not an atomic write)....

@AEgit the most recent developement version now includes the latest performance improvements. Could you please check what still needs improvement. Thanks!

Thanks for the feedback. I'll try to have a look at the remaining performance issues in the next days.

@AEgit We implemented some performance improvements recently. Can you please see if they might have fixed some of the issues you described in https://github.com/JabRef/jabref/issues/5071#issuecomment-554769666. Moreover, it would be good which...

I found some Easter eggs in the code. After eating them JabRef now feels more slim and responsive. In fact, for me all the performance problems mentioned in this issue...

@ilippert @AEgit thanks for the feedback.

I think something is seriously broken in the file writing algorithm in recent versions. I managed to corrupt my own library by exiting JabRef forcefully during the writing process. Also...

@koppor Wouldn't `docs/advanced-reading/citationrelations` be a good place for the documentation?

I wouldn't remove auto-saving. Actually, I feel this should be the standard behavior: why do I need to remember as a user to save the file?

That might lead to performance problems: saving might take a few seconds so in the worst case the save requests add up. The same with "Save all" etc. I think...