From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: Feature Request - Active and inactive links. Date: Tue, 11 Dec 2007 22:30:40 +0100 Message-ID: <87tzmoor5r.fsf@bzg.ath.cx> References: <3d6808890712030717s4aeccea3oe95960df850d4841@mail.gmail.com> <87bq8zcto6.fsf@bzg.ath.cx> <3d6808890712091651j17631cd6s7234351ac8f35532@mail.gmail.com> <87tzmptr34.fsf@bzg.ath.cx> <3d6808890712110523l5d369faaj5aaf1bcc87a1b55f@mail.gmail.com> <3d6808890712110524x66985a20h3340e9cbacbdadda@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J2Cgj-00018x-8F for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 16:30:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J2Cgh-00015u-AS for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 16:30:48 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J2Cgg-00015j-SX for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 16:30:46 -0500 Received: from ug-out-1314.google.com ([66.249.92.174]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J2Cgg-0001ts-NR for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 16:30:46 -0500 Received: by ug-out-1314.google.com with SMTP id a2so427875ugf.48 for ; Tue, 11 Dec 2007 13:30:45 -0800 (PST) In-Reply-To: (Christian Egli's message of "Tue, 11 Dec 2007 16:08:59 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Christian Egli Cc: emacs-orgmode@gnu.org Christian Egli writes: > Tim O'Callaghan 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