From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org,Gergely Risko <gergely@risko.hu>
Subject: Re: inhibit-message variant that doesn't even log to *Messages*
Date: Thu, 31 Jan 2019 10:52:22 +0200 [thread overview]
Message-ID: <85971BA9-DF67-4B12-A05B-1AF5F198AE0C@gnu.org> (raw)
In-Reply-To: <87h8dpuu4i.fsf@errge.nilcons.com>
On January 31, 2019 10:08:29 AM GMT+02:00, Gergely Risko <gergely@risko.hu> wrote:
> Hi,
>
> I use more and more packages that provide some functionality by doing
> something periodically.
>
> A recent example is sync-recentf:
> https://github.com/ffevotte/sync-recentf
>
> When sync-recentf decides to periodically save the recent file, a lot
> of
> messages get written with the `message' function.
>
> I worked around most if this with:
>
> (defadvice recentf-cleanup (around nce/recentf-cleanup activate)
> (let ((inhibit-message t))
> ad-do-it))
>
> 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.
>
> 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*)?
>
> Would there be willingness to merge this if I were to work on this?
>
> 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.
>
> Cheers,
> Gergely
Is there any problem in binding message-log-max to a nil value?
next prev parent reply other threads:[~2019-01-31 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 8:08 inhibit-message variant that doesn't even log to *Messages* Gergely Risko
2019-01-31 8:39 ` Robert Pluim
2019-01-31 8:52 ` Eli Zaretskii [this message]
2019-01-31 9:34 ` Gergely Risko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85971BA9-DF67-4B12-A05B-1AF5F198AE0C@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gergely@risko.hu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.