From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Limited #+INCLUDE ? Date: Tue, 27 Apr 2010 23:56:58 +0200 Message-ID: <4F178063-6E2B-43DA-8587-BFAF7239C613@gmail.com> References: <874oj2v2a6.fsf@tandberg.com> <87k4ruy5pd.fsf@mundaneum.com> <87eii26lzg.fsf@stats.ox.ac.uk> <878w89l2pq.wl%ucecesf@ucl.ac.uk> <87wrvtyln2.fsf@gmail.com> <878w88k8k7.fsf@stats.ox.ac.uk> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O6smD-0001sb-Na for emacs-orgmode@gnu.org; Tue, 27 Apr 2010 17:57:09 -0400 Received: from [140.186.70.92] (port=60691 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O6smB-0001rQ-10 for emacs-orgmode@gnu.org; Tue, 27 Apr 2010 17:57:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O6sm6-0007u1-2x for emacs-orgmode@gnu.org; Tue, 27 Apr 2010 17:57:06 -0400 Received: from mail-ew0-f214.google.com ([209.85.219.214]:38548) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O6sm5-0007tu-Sl for emacs-orgmode@gnu.org; Tue, 27 Apr 2010 17:57:02 -0400 Received: by ewy6 with SMTP id 6so5161607ewy.32 for ; Tue, 27 Apr 2010 14:57:00 -0700 (PDT) In-Reply-To: <878w88k8k7.fsf@stats.ox.ac.uk> 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: Dan Davison Cc: emacs-orgmode@gnu.org On Apr 27, 2010, at 9:19 PM, Dan Davison wrote: > Samuel Wales writes: > >> Another way to look at it is that this is an annotation mechanism. >> It >> can be used for any type of file or buffer. This would include text, >> websites (i.e. pointing to and annotating documents on the web), >> dired, source code, org files, html source, etc. >> >> Modifying existing link syntax will be difficult, especially because >> there might be additional features we need a year or two from now. >> For maximum flexibility and simplicity, this might be a good first >> use >> of extensible syntax. > > Hi Samuel, > > I'm not quite clear what you're referring to when you say "this" in > the > above sentences. Also, when you say "extensible syntax", are you > referring to the existing link syntax, or to a proposed extension? Samuel wrote about this a year ago. http://article.gmane.org/gmane.emacs.orgmode/11896/match=wales+extensible - Carsten