From: Vladimir Nikishkin <for_emacs-recentf-patch_2023-12-21@lockywolf.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 67946@debbugs.gnu.org
Subject: bug#67946: 30.0.50; [RFC PATCH] Add an option to not report "Wrote ..." when saving recentf.
Date: Mon, 25 Dec 2023 13:17:37 +0800 [thread overview]
Message-ID: <87wmt2505y.fsf@laptop.lockywolf.net> (raw)
In-Reply-To: <CADwFkmkJSXe4CWNJtwgjwJuJ4SihwPhgXpM1OnRFgJMZ=8FX1Q@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> Vladimir Nikishkin <for_emacs-recentf-patch_2023-12-21@lockywolf.net>
> writes:
>
>> I have the following setting in my init.el
>>
>> (add-hook 'buffer-list-update-hook 'recentf-track-opened-file)
>> (add-hook 'buffer-list-update 'recentf-save-list)
>>
>> The first one is the one recommended by describe-function recentf-mode,
>> and the second one is to make this switch persistent, and resistant to
>> emacs being killed.
>>
>> However, I am getting a lot of messages like
>> `Wrote /home/lockywolf/.emacs.d/recentf', which are not very helpful
>> normally.
>
> When are these messages helpful?
Are you suggesting to turn them off unconditionally?
It would make sense, I guess. It might be useful when debugging "why is
my recentf file not updated", but if such an issue arises, I guess,
instrumenting "recentf-save-list" is more of a straightforward thing?
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
next prev parent reply other threads:[~2023-12-25 5:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 3:26 bug#67946: 30.0.50; [RFC PATCH] Add an option to not report "Wrote ..." when saving recentf Vladimir Nikishkin
2023-12-21 9:37 ` Eli Zaretskii
2023-12-24 14:39 ` Stefan Kangas
2023-12-25 5:17 ` Vladimir Nikishkin [this message]
2023-12-25 12:25 ` Eli Zaretskii
2023-12-25 21:50 ` Stefan Kangas
2023-12-26 5:58 ` Vladimir Nikishkin
2023-12-26 12:41 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmt2505y.fsf@laptop.lockywolf.net \
--to=for_emacs-recentf-patch_2023-12-21@lockywolf.net \
--cc=67946@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).