From: Lars Ingebrigtsen <larsi@gnus.org>
To: reporter <laszlomail@protonmail.com>
Cc: "46153@debbugs.gnu.org" <46153@debbugs.gnu.org>
Subject: bug#46153: recentf should keep files in most recently used order
Date: Fri, 29 Jan 2021 06:47:36 +0100 [thread overview]
Message-ID: <87o8h8wayv.fsf_-_@gnus.org> (raw)
In-Reply-To: <JZMdwBfZ6SA3v2uPfawXsfR3RoFMtIF1nOlYwmx0t_KOThyGIBvG2sApc522BIfdx0LxlJVB2B5Yc2X5NQ5zdV5ozqqLrrOD_D5foRbruUI=@protonmail.com> (reporter's message of "Thu, 28 Jan 2021 14:43:51 +0000")
reporter <laszlomail@protonmail.com> writes:
> Apparently, this is all what's needed:
>
> (add-hook 'buffer-list-update-hook 'recentf-track-opened-file)
>
> So buffer-list-update-hook should be added to recentf-used-hooks
> in recentf.el
Some people would want the current behaviour, so I don't think doing
this by default would be the right thing to do, but I can certainly see
people who'd prefer recentf to work in this way.
So I've mentioned doing this `add-hook' in the recentf-mode doc string
in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-01-29 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 12:37 bug#46153: recentf should keep files in most recently used order laszlomail--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.46153.B.161183744421386.ack@debbugs.gnu.org>
2021-01-28 14:43 ` bug#46153: Acknowledgement (recentf should keep files in most recently used order) laszlomail--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-29 5:47 ` Lars Ingebrigtsen [this message]
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=87o8h8wayv.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=46153@debbugs.gnu.org \
--cc=laszlomail@protonmail.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 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.