I was finding that the use of org-agenda made my recent files list less than useful, by filling up the list with files that I rarely opened "by hand" with find-file. The following snippet, added to my org-config file, seems to have fixed things. ;;;--------------------------------------------------------------------------- ;;; Agenda files shouldn't get entries in the recentf-list ;;;--------------------------------------------------------------------------- (defun org-is-agenda-file (filename) (find (file-truename filename) org-agenda-files :key 'file-truename :test 'equal)) (require 'recentf) (pushnew 'org-is-agenda-file recentf-exclude) I mention this on the off-chance it's useful to someone else... cheers, r
Robert Goldman <rpgoldman@sift.info> writes:
> ;;;---------------------------------------------------------------------------
> ;;; Agenda files shouldn't get entries in the recentf-list
> ;;;---------------------------------------------------------------------------
Knowing about `recentf-exclude' will certainly help many users,
not only for excluding Org files.
Thanks,
--
Bastien
On 8/10/12 Aug 10 -2:21 AM, Bastien wrote:
> Robert Goldman <rpgoldman@sift.info> writes:
>
>> ;;;---------------------------------------------------------------------------
>> ;;; Agenda files shouldn't get entries in the recentf-list
>> ;;;---------------------------------------------------------------------------
>
> Knowing about `recentf-exclude' will certainly help many users,
> not only for excluding Org files.
>
> Thanks,
>
For what it's worth, a more fine-grained alternative would be to get
inside org-get-agenda-file-buffer and inhibit the recentf caching while
calling find-file inside there.
That would allow you to have an agenda file appear in the recent files
list IF it was opened through a manual use of find-file, but NOT if it
was opened as a side effect of loading an agenda.
This more fine-grained approach was a little more work than I wanted to
do, and didn't necessarily provide me a lot more value, so I didn't
bother with it. But someone else might find it worth coding up. Chacun
à son org configuration!
Cheers,
r
Robert Goldman <rpgoldman <at> sift.info> writes: > > On 8/10/12 Aug 10 -2:21 AM, Bastien wrote: > > Robert Goldman <rpgoldman <at> sift.info> writes: > > > >> ;;;--------------------------------------------------------------------------- > >> ;;; Agenda files shouldn't get entries in the recentf-list > >> ;;;--------------------------------------------------------------------------- > > > > Knowing about `recentf-exclude' will certainly help many users, > > not only for excluding Org files. > > > > Thanks, > > > > For what it's worth, a more fine-grained alternative would be to get > inside org-get-agenda-file-buffer and inhibit the recentf caching while > calling find-file inside there. > > That would allow you to have an agenda file appear in the recent files > list IF it was opened through a manual use of find-file, but NOT if it > was opened as a side effect of loading an agenda. > > This more fine-grained approach was a little more work than I wanted to > do, and didn't necessarily provide me a lot more value, so I didn't > bother with it. But someone else might find it worth coding up. Chacun > à son org configuration! > > Cheers, > r > > It seems that absolute paths are needed in the definition of org files. If org-agenda-files is defined using ~/org/.. this may not work since recentf uses absolute paths. Cheers, Mohamed