Updating the database should not block the Sublime usage

[aaltat]

When creating or updating the internal database, the operation can take quite a long time. Now those operations block the usage of the Sublime, which is not good practice. Make the command for updating the database as non blocking operations.

[idxn]

@aaltat I would like to have this feature. Could you please guide me how to implement this? I'm not sure I'm capable enough to do that but I'll give it a chance.

[aaltat]

Usually Sublime commands are blocking, but it should be possible to launch the database creation in a separate process and out of Sublime context. The problem is that, when it's out of Sublime context, we lose the way to communicate with back to Sublime (example how to communicate errors). And for that problem, I don't have a solution.

Instead of this, I would first try to make the database creation as fast as possible. First some profiling should be done and then improvements can be applied.

But if you want to tackle this issue, one should design how the communication back to Sublime is done.

[idxn]

Profiling should be easier then 👍