From: Carsten Dominik <carsten.dominik@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: SUMMARY: [Feature Request] Make property-drawers exportable
Date: Wed, 25 Sep 2013 12:56:18 +0200 [thread overview]
Message-ID: <603659F2-7FCC-4920-9ABF-2318F9FE5D5C@gmail.com> (raw)
In-Reply-To: <87had9tboh.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 25.9.2013, at 12:53, Thorsten Jolitz <tjolitz@gmail.com> wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> 3. The only exception to this rule are property drawers, which will
>> currently not be exported by any of the backends. Nicolas
>> proposed to define a derived backend that does export the property
>> drawer, or he proposed to use macros to extract specific properties
>> to include into the exported file. Both are viable options.
>
>> One possible remaining option would be to introduce user variables
>> org-BACKEND-format-property-drawer-function in analogy
>> org-BACKEND-format-drawer-function. This would provide an easy way
>> to configure export of the property drawer as a whole, in a way
>> that could be file-local.
>>
>> I would like to have this option
>
> +1
>
> property drawers are just too useful to restrict them to Org-mode's
> internal meta-data, and anything that makes it easier to export them
> when used for 'use case' related meta-data or as simple DB is welcome.
To be sure: Nicolas' argument that other functions dump data into
the property drawer is completely right, and so I also think that
one would hardly ever want to export the complete drawer. But
through a function that selects (or deselects), it is useful.
- Carsten
>
> --
> cheers,
> Thorsten
>
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2013-09-25 10:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 9:53 [Feature Request] Make property-drawers exportable Thorsten Jolitz
2013-06-17 14:33 ` Nicolas Goaziou
2013-06-17 15:48 ` Thorsten Jolitz
2013-06-17 18:54 ` Marcin Borkowski
2013-06-17 19:04 ` Nicolas Goaziou
2013-06-17 20:03 ` Thorsten Jolitz
2013-09-25 9:31 ` Carsten Dominik
2013-09-25 9:34 ` Carsten Dominik
2013-09-25 10:33 ` SUMMARY: " Carsten Dominik
2013-09-25 10:53 ` Thorsten Jolitz
2013-09-25 10:56 ` Carsten Dominik [this message]
2013-09-26 8:44 ` Marcin Borkowski
2013-09-25 11:51 ` Nicolas Goaziou
2013-09-25 12:08 ` Carsten Dominik
2013-09-25 12:13 ` Nicolas Goaziou
2013-09-25 12:26 ` Carsten Dominik
2013-09-25 20:57 ` Nicolas Goaziou
2013-09-26 11:28 ` Carsten Dominik
2013-09-26 11:48 ` Nicolas Goaziou
2013-09-26 11:51 ` Carsten Dominik
2013-09-26 14:33 ` Nicolas Goaziou
2013-09-26 16:06 ` Carsten Dominik
2013-09-25 12:52 ` Christian Moe
2013-09-25 12:12 ` Thorsten Jolitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=603659F2-7FCC-4920-9ABF-2318F9FE5D5C@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.