From: Bastien <bzg@altern.org>
To: tony day <tonyday567@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: org reserved and special words in drawers
Date: Mon, 24 Dec 2012 02:49:03 +0100 [thread overview]
Message-ID: <87a9t4te28.fsf@bzg.ath.cx> (raw)
In-Reply-To: <5750CCC1-3900-4FDC-8525-A51B7D85958C@gmail.com> (tony day's message of "Wed, 7 Nov 2012 14:33:07 +1100")
Hi Tony,
tony day <tonyday567@gmail.com> writes:
> I've been thinking about a patch for org-mode that would give an
> option to place various org concepts in a drawer rather than
> automatically in the body of the document. The overall idea is that
> for some use cases, it makes sense to disturb the underlying content
> as little as possible. In other words, we could then /apply/ org-mode
> on a document rather than transforming a document into an org
> document.
>
> Is this doable or is it a crazy amount of work for little benefit?
What is doable is to try to enhance Org so that less stuff come in the
way, sure.
What we may think about is a "Org readable exchange format (oref?)",
which would take the output of Nicolas' parser, export it in Org-mode
using some specific properties like "TAGS:" "TODO:" etc.
> The org concepts I've penciled in are:
>
> ** tags
>
> What might be the best scheme for defining tags as properties rather
> than in headlines?
See above.
> ** scheduled, closed, deadline
>
> It should be possible to put these in drawers.
There is a plan for this, yes.
> ** =todo=
>
> Can we put =todo= keywords in drawers but still easily use all the
> org-mode technology surrounding them?
See above.
> ** item
>
> Would it be at all possible to define an item without actually adding
> a header? One solution that comes to mind is to define an item (or a
> subtree in other words) as all content until the next properties drawer.
>
> Is there anything else missing from this list?
Maybe you can start working on a org-e-oref exporter, storying *all*
metadata into properties? ... Don't know where it will lead, but who
knows?
--
Bastien
next prev parent reply other threads:[~2012-12-24 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 13:53 BUG ? [new HTML exporter] subtree: newline and slash Giovanni Ridolfi
2012-11-06 16:48 ` Nicolas Goaziou
2012-11-06 17:03 ` Giovanni Ridolfi
2012-11-06 17:20 ` Nicolas Goaziou
2012-11-07 3:33 ` org reserved and special words in drawers tony day
2012-12-24 1:49 ` Bastien [this message]
2012-12-28 23:53 ` Tony Day
2012-12-29 20:00 ` Bastien
2012-12-31 0:19 ` Tony Day
2012-11-07 12:15 ` solved (Re: BUG ? [new HTML exporter] subtree: newline and slash) Giovanni Ridolfi
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=87a9t4te28.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=tonyday567@gmail.com \
/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).