https://bugs.kde.org/show_bug.cgi?id=437337
Waqar Ahmed changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util
|it
https://bugs.kde.org/show_bug.cgi?id=437337
Nate Graham changed:
What|Removed |Added
Version Fixed In||23.04
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=437337
Waqar Ahmed changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/util
|
https://bugs.kde.org/show_bug.cgi?id=437337
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=437337
--- Comment #4 from Nate Graham ---
That seems easily optimizable by only writing to the config file when a new
file is opened, not when the session itself is loaded, no? And in the case
where multiple files are opened by the same action, they could be
https://bugs.kde.org/show_bug.cgi?id=437337
--- Comment #3 from Christoph Cullmann ---
:P Unfortunately I use NFS homes daily :P
e.g. if you open your session and it has 100 files open, you will now write 100
times the full session config back in worst case.
If we just delay that with say a 10
https://bugs.kde.org/show_bug.cgi?id=437337
--- Comment #2 from Nate Graham ---
Yeah, there are definitely trade-offs involved. However I don't know how common
the NFS home directory use case is, and perhaps we could optimize it. And I
think writing to the config file every time a document is ope
https://bugs.kde.org/show_bug.cgi?id=437337
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #1 from Chris
