|
From: | Dmitry Gutov |
Subject: | bug#66993: [PATCH] project.el: avoid asking user about project-list-file lock |
Date: | Wed, 8 Nov 2023 23:03:43 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 |
On 08/11/2023 17:36, Spencer Baugh wrote:
Separately: Currently, even without any locking issues, if there are multiple Emacsen then project-list-file just contains the project--list of the last one to write. So they're constantly clobbering each others' added and removed projects. If we do the writes more rarely, then we could try to read project-list-file first and add or remove the projects that were added or removed during the life of this Emacs instance, instead of just blindly writing out project--list. Then if there are multiple Emacsen around, their changes to project--list won't clobber each other, they'll just be cleanly merged. Does that sound reasonable? Either way, I can implement this.
If you're sure that the added utility is worth the complication in the code, why not.
Please post some performance measurements for before/after, though.E.g. how long project--write-project-list takes without re-reading the file, and with the new, merging approach. Though it's probably okay.
BTW, that reminds me of the Fish shell's history merging between parallel sessions. I think it was automatic in some version, and now it's manual again (https://github.com/fish-shell/fish-shell/issues/825).
[Prev in Thread] | Current Thread | [Next in Thread] |