From: Bastien <bzg@altern.org>
To: Christian Egli <christian.egli@novell.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Feature Request - Active and inactive links.
Date: Tue, 11 Dec 2007 22:30:40 +0100 [thread overview]
Message-ID: <87tzmoor5r.fsf@bzg.ath.cx> (raw)
In-Reply-To: <loom.20071211T160530-39@post.gmane.org> (Christian Egli's message of "Tue, 11 Dec 2007 16:08:59 +0000 (UTC)")
Christian Egli <christian.egli@novell.com> writes:
> Tim O'Callaghan <tim.ocallaghan <at> gmail.com> writes:
>
>> Yes. My idea was essentially, when i ask org to create an agenda
>> buffer, it knows to auto-pull and process each all of these
>> active links, so as to be able to display them in my Agenda.
>
> I still don't quite understand why you do not use existing infrastructure such
> as the include statement in diary files and the org-agenda-files variable which
> lets you define a list files to be included for agenda generation.
The include statement in the diary file is enough for inclusion of diary
files. Adding files in org-agenda-files would be enough when we don't
need to have a certain file included depending on the content we're
processing.
I think the rationale behind Tim's idea is:
- make it possible to *dynamically* process a list of agenda files
(instead of the static org-agenda-files)
- make it possible to fetch remote/shared resources so that you can
*collaborate* over the network with Org files.
The horizon is to handle Org files in a more dynamic, modular,
distributed way © ... But maybe Tim has better/simpler arguments.
--
Bastien
prev parent reply other threads:[~2007-12-11 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 15:17 Feature Request - Active and inactive links Tim O'Callaghan
2007-12-09 23:52 ` Bastien
[not found] ` <3d6808890712091651j17631cd6s7234351ac8f35532@mail.gmail.com>
2007-12-10 0:52 ` Tim O'Callaghan
2007-12-10 23:49 ` Christian Egli
2007-12-11 11:21 ` Bastien
[not found] ` <3d6808890712110523l5d369faaj5aaf1bcc87a1b55f@mail.gmail.com>
2007-12-11 13:24 ` Tim O'Callaghan
2007-12-11 14:59 ` Bastien
2007-12-11 16:08 ` Christian Egli
2007-12-11 21:30 ` Bastien [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=87tzmoor5r.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=christian.egli@novell.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).