From: mohamed <mohamed.hibti@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org agenda and recent files list....
Date: Mon, 3 Feb 2014 09:55:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20140203T105201-257@post.gmane.org> (raw)
In-Reply-To: 5025717E.5010108@sift.info
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
prev parent reply other threads:[~2014-02-03 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 4:01 Org agenda and recent files list Robert Goldman
2012-08-10 7:21 ` Bastien
2012-08-10 20:39 ` Robert Goldman
2014-02-03 9:55 ` mohamed [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20140203T105201-257@post.gmane.org \
--to=mohamed.hibti@gmail.com \
--cc=emacs-orgmode@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).