You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two things here that are both aimed at reducing the amount of
resource clutter:
1. I've seen many tmp files left. Looking at the code, it seems to me
like a reasonable thing to get rid of them when a file is saved. I
did this via adding `tide-remove-tmp-file` on `after-save-hook`.
2. I also saw that there is a general tendency to accumulate many
servers since they're never removed (actually, more than just the
servers -- the whole project resources are kept, but the server is
the main problem wrt resources). This is also mentioned in #256.
So I implemented a function that scans all buffers and cleanup all
projects that have no live buffers. It looks to me like a good idea
to do this, since you can just kill old buffers to reduce resource
usage. (And killing old buffers is more obvious than explicitly
openning the server list to kill old ones, especially since there's
no way to tell if a server is used by some buffer or not.)
(I added this function onto `kill-buffer-hook`, but if that's too
extreme, then a more mild option is to not do that and just let
people add it themselves.)
0 commit comments