all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37772@debbugs.gnu.org
Subject: bug#37772: 26.3; Doc of recentf, particularly `recentf-list'
Date: Thu, 17 Oct 2019 15:41:09 +0000 (UTC)	[thread overview]
Message-ID: <15372348-a7e5-4b90-b8ab-bee94a484b55@default> (raw)
In-Reply-To: <877e54m6je.fsf@gnus.org>

> > Many users use recentf.  Likewise, libraries.  Nowhere is it said
> > what order the files are listed in, i.e., the order of the elements of
> > `recentf-list'.  The answer is apparently that, by default at least,
> > a file is pushed to the front of the list when it is "opened" or
> > written.
> >
> > A more exact answer is that `recentf-list' is in reverse
> > chronological order of calls to `recentf-track-opened-file'.
> > And by default that function is added to these hooks:
> > `find-file-hook' and `write-file-functions'.
> 
> I think that seems pretty self-evident -- the doc strings talk about
> "most recent" etc, so what other ordering could be meant?

It's not obvious at all.  That the 30 most recently
opened files are listed says _nothing_ about the
order in which they're listed.

And nothing is said about the situations when (by
default) the list (`recentf-list') is updated.
The answer is in the hooks.  It's not about
re-selecting the window of a file buffer or
changing a file outside Emacs, for instance.
(Not by default, at least.)

> So I don't see anything to fix here and I'm closing this bug report.

Unfortunate.





  reply	other threads:[~2019-10-17 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 22:45 bug#37772: 26.3; Doc of recentf, particularly `recentf-list' Drew Adams
2019-10-17  2:48 ` Lars Ingebrigtsen
2019-10-17 15:41   ` Drew Adams [this message]
2019-10-17 17:11 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15372348-a7e5-4b90-b8ab-bee94a484b55@default \
    --to=drew.adams@oracle.com \
    --cc=37772@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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.