From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 60470-done@debbugs.gnu.org
Subject: bug#60470: 26.3; Doc string of `recentf-keep'
Date: Mon, 02 Jan 2023 15:00:15 +0200 [thread overview]
Message-ID: <83r0wd1480.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488EEE62BD88D57676569C5F3F69@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sun, 1 Jan 2023 22:31:55 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "60470-done@debbugs.gnu.org" <60470-done@debbugs.gnu.org>
> Date: Sun, 1 Jan 2023 22:31:55 +0000
>
> > I've rad the doc string, and I see nothing wrong with it. In
> > particular, I did find there the explanation of what "keeping" means.
> >
> > So I'm closing this bug.
>
> FWIW, I don't see any such explanation, in any doc string.
Here it is:
List of regexps and predicates for filenames kept in the recent list.
> Other than searching thus in the code, I see no way for a
> user to know what "keep" means. Does it refer to keeping
> persistently, i.e., not removing when saving? Does it
> refer to keeping after the buffer for the file is killed?
> When a "cleanup" occurs? "Keep" in what way, wrt what?
Here's the answer:
(define-minor-mode recentf-mode
"Toggle keeping track of opened files (Recentf mode).
This mode maintains a list of recently opened files and makes it
easy to visit them. The recent files list is automatically saved
across Emacs sessions.
There's also a short explanation in the user manual:
If you enable Recentf mode, with ‘M-x recentf-mode’, Emacs maintains
a list of recently opened files. To open a file from this list, use the
‘M-x recentf-open’ command. When this mode is enabled, the ‘File’ menu
will include a submenu that you can use to visit one of these files.
‘M-x recentf-save-list’ saves the current ‘recentf-list’ to a file, and
‘M-x recentf-edit-list’ edits it.
> We give users two options for filtering the recentf list.
> The doc string of one seems clear enough: it prevents
> some file names _from being added_ to the list. The
> other doc string doesn't speak to the presumed _removal_
> operations for which it prevents removal. Its predicates
> and regexps prevent removal of certain files - but what
> is it that would otherwise cause their removal?
The original report didn't mention recentf-exclude. Since you now add
it to the issue, I've looked that up:
(defcustom recentf-exclude nil
"List of regexps and predicates for filenames excluded from the recent list.
When a filename matches any of the regexps or satisfies any of the
predicates it is excluded from the recent list.
A predicate is a function that is passed a filename to check and that
must return non-nil to exclude it."
Sounds perfectly clear to me, and the difference between recentf-keep
and recentf-exclude is also very clear.
> Would you mind pointing to the part of the doc string
> that you think explains what "keeping" means? I really
> don't see it.
See above.
next prev parent reply other threads:[~2023-01-02 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 16:39 bug#60470: 26.3; Doc string of `recentf-keep' Drew Adams
2023-01-01 17:51 ` Eli Zaretskii
2023-01-01 22:31 ` Drew Adams
2023-01-02 13:00 ` Eli Zaretskii [this message]
2023-01-02 17:48 ` Drew Adams
2023-01-02 17:56 ` 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=83r0wd1480.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60470-done@debbugs.gnu.org \
--cc=drew.adams@oracle.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).