Re: xref and leaving "temporary" buffers open

[martin rudalics]

> Better for xref to cache the info it gathered from the buffer (assuming
> that's significantly smaller, and faster to access, than the buffer).

Obviously.  But I'm afraid that's not always feasible.

> Functions for deleting some buffers based on such buffer properties
> would also be useful. In the projects case, the buffer would not
> actually be deleted until there was only one project property left.

We'd need a smart version of midnight's `clean-buffer-list'.

martin