>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.

I am saving recentf files on each new visited file or killed buffer
because, well, why wouldn't I? Why would I risk losing even a single
recentf entry if the impact of IO on an nvme is negligible, so I am
seeing this message all the time.

I have updated the patch, calling the variable
`recentf-inhibit-messages', because this is probably a better name, and
I have also made it a boolean.

I don't think that "saveplace" and "recentf" should share a variable,
because they are different packages, and people might be using them in
a different way.