From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Limited #+INCLUDE ?
Date: Tue, 27 Apr 2010 23:56:58 +0200 [thread overview]
Message-ID: <4F178063-6E2B-43DA-8587-BFAF7239C613@gmail.com> (raw)
In-Reply-To: <878w88k8k7.fsf@stats.ox.ac.uk>
On Apr 27, 2010, at 9:19 PM, Dan Davison wrote:
> Samuel Wales <samologist@gmail.com> 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
next prev parent reply other threads:[~2010-04-27 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:25 Limited #+INCLUDE ? Giles Chamberlin
2010-04-26 8:32 ` Sébastien Vauban
2010-04-26 19:40 ` Dan Davison
2010-04-27 0:34 ` Mark Elston
2010-04-27 2:19 ` Dan Davison
2010-04-28 0:52 ` Mark Elston
2010-04-27 8:27 ` Eric S Fraga
2010-04-27 10:25 ` Darlan Cavalcante Moreira
2010-04-27 15:12 ` Eric Schulte
2010-04-27 17:26 ` Dan Davison
2010-04-27 17:58 ` Eric Schulte
2010-04-27 18:27 ` Giles Chamberlin
2010-04-27 17:52 ` Samuel Wales
2010-04-27 19:19 ` Dan Davison
2010-04-27 21:56 ` Carsten Dominik [this message]
2010-04-29 23:14 ` Samuel Wales
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=4F178063-6E2B-43DA-8587-BFAF7239C613@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=davison@stats.ox.ac.uk \
--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).