From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Feature Request - Active and inactive links. Date: Tue, 11 Dec 2007 12:21:03 +0100 Message-ID: <87tzmptr34.fsf@bzg.ath.cx> References: <3d6808890712030717s4aeccea3oe95960df850d4841@mail.gmail.com> <87bq8zcto6.fsf@bzg.ath.cx> <3d6808890712091651j17631cd6s7234351ac8f35532@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J23Av-0001Vg-Qm for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 06:21:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J23Ar-0001Rv-TD for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 06:21:21 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J23Ar-0001Ro-NI for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 06:21:17 -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 1J23Aq-0003pz-CT for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 06:21:17 -0500 Received: by ug-out-1314.google.com with SMTP id a2so237848ugf.48 for ; Tue, 11 Dec 2007 03:21:08 -0800 (PST) In-Reply-To: <3d6808890712091651j17631cd6s7234351ac8f35532@mail.gmail.com> (Tim O'Callaghan's message of "Mon, 10 Dec 2007 01:51:00 +0100") 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: Tim O'Callaghan Cc: org-mode list Hi Tim, thanks for the details. I think I got confused because I couldn't understand what you mean by a link being "processed" when compiling the agenda. Now I understand that it means some kind of inclusion. So the issue seems twofold: 1. the first issue is about *including* external Org files (or other external resources, although I'm not sure to understand what does that mean); 2. the second issue is that of *processing* links to external resources when using your Org file as a source for other purposes (agenda view, export, etc.) I think both issues are very interesting but should be carefully (and maybe separately) thought. You're speaking about a link that would include the targetted Org file into the list of agenda files. Then attaching meta-data to this link, you would control how the building of the agenda should process the link (adding category, etc.) Some example of what we could do: - a link to an Org file that should be considered part of the master file (at any time: agenda view, export, etc.) This could be a new link type like "org:" org:~/home/org/header.org - a link to a file that should be included for specific export: #+BEGIN_LaTeX org:~/home/org/latex_footer.org #+END_LaTeX or maybe, if it's not ambigous: org:latex:~/home/org/latex_footer.org - a link to a file that should only be processed in agenda views: org:agenda:~/home/org/other-todo.org - ... and maybe only for a specific agenda view org:agenda:n~/home/org/other-todo.org ("n" being the name of the command key in org-agenda-custom-commands) Where you thinking of something like that? I'm not sure on how to integrate your idea about specifying categories, and I doubt this is particularily relevant: the links already belong to entries that will be categorized. I'm not sure although about your example with iCal. Do you think it could fit with the picture above? Thanks for this neat idea. I'm sure we're getting somewhere... -- Bastien