Re: Observing lags or never ending processes

[Jean Louis <bugs@gnu.support>]

* Emanuel Berg <incal@dataswamp.org> [2022-09-22 16:15]:
> Jean Louis wrote:
> 
> > I will try to monitor it, and minimize buffers. Some buffers
> > remain open and it accumulates to 4000 buffers.
> 
> Should automate that, often when that happens it isn't that
> you have 4000 buffers in general but instead there are 2-3 bad
> guys that produce the bulk of them, so those are the ones you
> should identify and have them explicitely kill buffer when
> they are done with whatever they are doing.

Having those buffers is convenient. Imagine list of people like
customers, then you click on one and review history, then you kill
that buffer, that is why you come back to previous one. It is
convenient.

Otherwise, I would need to pass function with arguments to newly
generated buffer to be able to remember how to construct the previous
one.

I would say, one could make some buffer function to kill the buffer if
it was not re-visited in some specific time. It would mean to install
timer for it.

Is there function which can sense that user switched to some buffer?

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/