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: Sat, 11 Mar 2023 08:52:06 +0200 Message-ID: <83pm9fye3t.fsf@gnu.org> References: <20230310110747.4hytasakomvdyf7i.ref@Ergus> <20230310110747.4hytasakomvdyf7i@Ergus> <83a60kzmj6.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18418"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Ergus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 11 07:53:25 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 1pat6Z-0004Xi-VO for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Mar 2023 07:53:24 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pat5u-0000V9-CW; Sat, 11 Mar 2023 01:52:44 -0500 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 1pat5f-0000UR-0e for emacs-devel@gnu.org; Sat, 11 Mar 2023 01:52:30 -0500 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 1pat5d-0004Bz-PD; Sat, 11 Mar 2023 01:52:26 -0500 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=3N0MaXlL4NiwzdEfmipG8Jq8xr2jGEHUkiAGUk1LlzI=; b=VNLHf8xuR54c 2xCPaQUljgrM7QDQhJgWi1+1f4npc3oiv2qvtUr6kAuDBV35oUMGO+pE95x2x1OQMxQ6QVakCDjnA xIoT9GCXTkAUmNdO9lgpxlPPbXAEN2O0wbFvQFJU3U/X7LcmQg5ga4FpbTstTau1hvAHwY4/CPLkP ffv+q0rpfGOCScV7++0UvukhXqDLXb1cdOybZJfUSx4Pr5zBF5SXi2qE8NTLK3jAgcMDL05qyv8WO ObSHzFsUJh+f2LhgIMWVj7p/BxKA56ifJHbIbWxwrapPS5+FcNoUOdE739QM3/u3XcN4DmAgF3ZhT k8BGIM11nzQJhgYhYU2t4w==; 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 1pat5a-0002nL-KQ; Sat, 11 Mar 2023 01:52:25 -0500 In-Reply-To: (message from Ergus on Fri, 10 Mar 2023 22:30:42 +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:304275 Archived-At: > Date: Fri, 10 Mar 2023 22:30:42 +0100 > From: Ergus > > >> 2) IF it doesn't impact performance... Is it possible somehow to improve > >> the gc message to have more useful information; or at least; to control > >> the no-log in order to have some outputs in the *Message* buffer? > > > >How will a more detailed GC message help? > > > > Hi, > > I explained wrongly. These were somehow two almost independent questions. The more detailed GC and having a logging alternative are useful for debugging purposes. Because (for example) I don't know exactly how many GC were executed during the indentation. > > So they are related but not directly. I think I understood, but my question still stands: how will a more detailed GC report help you in what you are trying to do? You can see the kind of data GC returns in the doc string of garbage-collect, and you can see that in action if you invoke "M-x garbage-collect RET" by hand. Please tell how will this data help you do what you want to do.