unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Observing lags or never ending processes
Date: Fri, 23 Sep 2022 08:30:18 +0300	[thread overview]
Message-ID: <Yy1Eandfxa9Fg3x2@protected.localdomain> (raw)
In-Reply-To: <YyzFyK2UtUInPx+I@protected.localdomain>

* Jean Louis <bugs@gnu.support> [2022-09-23 07:30]:
> * 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?

I wish to ask if there is function that can tell that user did not
view the buffer for longer time? It is about self destruction if
unused for some time.

Then the buffer could delete itself by using timer.

-- 
Jean

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

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



  reply	other threads:[~2022-09-23  5:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  6:59 Observing lags or never ending processes Jean Louis
2022-09-11  7:06 ` Eli Zaretskii
2022-09-11 12:36   ` Jean Louis
2022-09-11 13:16     ` Eli Zaretskii
2022-09-11 13:31       ` Jean Louis
2022-09-11 20:21       ` Jean Louis
2022-09-12  2:26         ` Eli Zaretskii
2022-09-12  5:53           ` Jean Louis
2022-09-12 11:19             ` Eli Zaretskii
2022-09-12 12:35               ` Jean Louis
2022-09-12  7:50           ` Jean Louis
2022-09-12 11:32             ` Eli Zaretskii
2022-09-16 19:06       ` Jean Louis
2022-09-17  6:00         ` Eli Zaretskii
2022-09-19 18:43           ` Jean Louis
2022-09-19 19:01             ` Eli Zaretskii
2022-09-20  4:42               ` Jean Louis
2022-09-20  7:54                 ` Emanuel Berg
2022-09-22 20:30                   ` Jean Louis
2022-09-23  5:30                     ` Jean Louis [this message]
2022-09-23  6:13                     ` Eli Zaretskii
2022-09-23  8:17                       ` Jean Louis
2022-09-23 10:42                         ` Eli Zaretskii
2022-09-23 14:16                           ` Jean Louis
2022-09-24 15:30                             ` Emanuel Berg
2022-09-23 11:30                     ` Emanuel Berg
2022-09-20 11:20                 ` Eli Zaretskii
2022-09-20 18:17                   ` Emanuel Berg
2022-09-19 23:11             ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-11 15:57   ` Jean Louis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yy1Eandfxa9Fg3x2@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).