From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Indentation and gc Date: Tue, 14 Mar 2023 14:30:39 +0200 Message-ID: <83ttynsefk.fsf@gnu.org> References: <20230310110747.4hytasakomvdyf7i.ref@Ergus> <20230310110747.4hytasakomvdyf7i@Ergus> <87a60k657y.fsf@web.de> <838rg4zmg9.fsf@gnu.org> <87ttys4dge.fsf@web.de> <83sfebyepp.fsf@gnu.org> <87ttyru4zt.fsf@web.de> <83fsabyb41.fsf@gnu.org> <87mt4jtpqf.fsf@web.de> <83ilf7wi48.fsf@gnu.org> <878rg3wh2f.fsf@localhost> <83cz5fwggd.fsf@gnu.org> <871qlvwg1s.fsf@localhost> <83a60jwf9l.fsf@gnu.org> <871qluuk3y.fsf@localhost> <831qluuj7e.fsf@gnu.org> <87v8j6t3i9.fsf@localhost> <83v8j6t2ib.fsf@gnu.org> <87zg8gbsch.fsf@localhost> <838rg0u0fd.fsf@gnu.org> <87wn3ky7rz.fsf@localhost> <878rg034e3.fsf@no.lan> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29909"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Gregor Zattler Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 14 13:31:36 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pc3oW-0007c4-89 for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Mar 2023 13:31:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pc3ns-0003Nr-G8; Tue, 14 Mar 2023 08:30:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pc3nk-0003KZ-4X for emacs-devel@gnu.org; Tue, 14 Mar 2023 08:30:54 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pc3nj-0005U6-Q5; Tue, 14 Mar 2023 08:30:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=lWGCem512l5Z7nnvflrQ3CGdgoPqyFd3ATR1LhxqEp8=; b=CgMDKRHuKwhw lI5lmR6a5QzBUifctFASYvj9f/v1Xe1D77ji6++Qv+w6JbukrG57DfPVo/Sarj7piGVQs/Ar+It2x pJ+8NmbyLyjqmbbZdlBsGIA7JmnwOi9mIeS1o6gYw8CPPgctM0j5PnzySv3zGYDMmeGO0pCRJJ8te v49oM85XISYdu9uT5bLlCKvWaHa8kaBmqLNpyi1vFQCq8nuGfGD8WXekZgjQp91wE+hYnz9V7B9TI pRYiFH9GKBOPZg0JTM5M03G9+yGBzpD4RcVsNNggrC5t/KS9kt1lz94yxl17XS2B+ZI7Gjd+8Q9u3 Gb3pXW4K0Caz004Z7+3iyw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pc3nh-0001KB-FC; Tue, 14 Mar 2023 08:30:47 -0400 In-Reply-To: <878rg034e3.fsf@no.lan> (message from Gregor Zattler on Mon, 13 Mar 2023 19:14:28 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304434 Archived-At: > From: Gregor Zattler > Date: Mon, 13 Mar 2023 19:14:28 +0100 > > Since you provide emacs-uptime at session end, I think > it would be useful to know total Emacs idle time also. > I have no idea if that's feasible, though. Why would it be useful, and what kind of information can we glean from that? I'm guessing that you assume when Emacs is idle it cannot possibly cons any memory (which is true), but my point is different: did you really see any production Emacs session that stays idle for prolonged times? E.g., in the session where I'm typing this I have 10 timers, 5 of which run at least once every 10 sec, and 3 run 2 or more times a second.