From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: inhibit-message variant that doesn't even log to *Messages* Date: Thu, 31 Jan 2019 10:52:22 +0200 Message-ID: <85971BA9-DF67-4B12-A05B-1AF5F198AE0C@gnu.org> References: <87h8dpuu4i.fsf@errge.nilcons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="150460"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: K-9 Mail for Android To: emacs-devel@gnu.org,Gergely Risko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 31 09:53:34 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gp86H-000d1x-4X for ged-emacs-devel@m.gmane.org; Thu, 31 Jan 2019 09:53:33 +0100 Original-Received: from localhost ([127.0.0.1]:51015 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gp86G-00044h-47 for ged-emacs-devel@m.gmane.org; Thu, 31 Jan 2019 03:53:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51606) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gp85M-00044b-Lk for emacs-devel@gnu.org; Thu, 31 Jan 2019 03:52:37 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57180) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gp85K-0000SD-PW; Thu, 31 Jan 2019 03:52:34 -0500 Original-Received: from [176.12.202.2] (port=51134 helo=[10.164.245.253]) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1gp85B-0007n4-6n; Thu, 31 Jan 2019 03:52:33 -0500 In-Reply-To: <87h8dpuu4i.fsf@errge.nilcons.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232854 Archived-At: On January 31, 2019 10:08:29 AM GMT+02:00, Gergely Risko wrote: > Hi, >=20 > I use more and more packages that provide some functionality by doing > something periodically=2E >=20 > A recent example is sync-recentf: > https://github=2Ecom/ffevotte/sync-recentf >=20 > When sync-recentf decides to periodically save the recent file, a lot > of > messages get written with the `message' function=2E >=20 > I worked around most if this with: >=20 > (defadvice recentf-cleanup (around nce/recentf-cleanup activate) > (let ((inhibit-message t)) > ad-do-it)) >=20 > My problem is that, these messages still get logged to *Messages*, so > if > I set the frequency to every 15 seconds, and try to debug something > unrelated in Elisp, then these messages get to be annoying a bit=2E >=20 > Would there be any downside to providing an additional variable (under > the name `inhibit-message-fundamentally' or such) that would inhibit > message printing altogether (echo area AND *Messages*)? >=20 > Would there be willingness to merge this if I were to work on this? >=20 > flet, letf, cl-letf and the like will not work for me, because some of > the messages I'm interested in temporarily disabling are coming from C > code=2E >=20 > Cheers, > Gergely Is there any problem in binding message-log-max to a nil value?