If we can agree on a name for a "be quiet" variable, I will patch saveplace to do the same. That one has been annoying me for a while, too. It uses write-region without an option to suppress its "Wrote" message. Or, in contrast, savehist uses write-region and produces a message only when called interactively, otherwise it's quiet. Perhaps that's even better? On Thu, Feb 13, 2025 at 5:07 AM Ship Mints wrote: > These kinds of messages interfere with minibuffer use when they appear. My > recentf timer is hourly, yet I still notice it from time to time. I > forcibly suppress the message in a messier way than I'd prefer. > > It was on my list to one day submit a patch for the same thing with a > defcustom called recentf-inhibit-messages. > > On Thu, Feb 13, 2025 at 3:15 AM Stefan Kangas > wrote: > >> Eli Zaretskii writes: >> >> >> From: Lockywolf >> >> Cc: eliz@gnu.org, >> >> stefankangas@gmail.com, >> >> Lockywolf >> >> Date: Thu, 13 Feb 2025 12:04:30 +0800 >> >> >> >> +(defcustom recentf-verbosity 1 >> >> + "Whether to show verbose messages about low-level recentf actions. >> >> +0 means to not show debugging messages related to the recentf >> machinery. >> >> +1 means show messages that were printed by default on Emacs <= 31.1." >> >> + :group 'recentf >> >> + :type 'integer >> >> + :version "31.1") >> > >> > I think referring to the "Wrote..." messages as "debugging" is >> > incorrect, since this is the normal Emacs operation when saving a >> > buffer. >> >> In context, and from the users point of view, this is not something one >> should normally need to care about or look at. I'd consider this >> debugging output, myself. Just my two cents, of course. >> >> >> >>