From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [Feature Request] Make property-drawers exportable
Date: Mon, 17 Jun 2013 11:53:24 +0200 [thread overview]
Message-ID: <8738shvzaj.fsf@gmail.com> (raw)
Hi List,
for me property-drawers are a very useful feature of Org-mode, since
the need to store meta-data for a document is so frequent and
property-drawers are human- and machine-readable, easy to handle
interactively and programmatically, and avoid all that nasty redundancy
and accidental variation of giving meta-data as free text.
However, property-drawers are not exported except separating blank
lines. This is a real pity in my eyes, since parts of an Org-mode
document that can't be exported are visible only to the author of the
document and a few fellows that use the raw Org document too. This might
make sense in some cases, but in others the property information should
be visible in the exported docs too.
I don't really consider the export options (#+TITLE, #+AUTHOR etc) as a
replacement for property drawers, in some situations I would like to use
property drawers and see them exported.
So here is my feature request, at least for the most important backends
ASCII, HTML and LATEX: add a function for property drawer export and an
export option to turn on/off this export.
PS
the status-quo of property-drawer export at the moment:
1. backends that (seem to) deal with property drawers:
,---------------------------------------------------------------------------
| 3 matches for "property-drawer" in buffer: ox-html.el
| 83: (property-drawer . org-html-property-drawer)
| 2893:(defun org-html-property-drawer (property-drawer contents info)
| 2894: "Transcode a PROPERTY-DRAWER element from Org to HTML.
|
| 3 matches for "property-drawer" in buffer: ox-odt.el
| 66: (property-drawer . org-odt-property-drawer)
| 3017:(defun org-odt-property-drawer (property-drawer contents info)
| 3018: "Transcode a PROPERTY-DRAWER element from Org to ODT.
|
| 1 match for "property-drawer" in buffer: ox-org.el
| 91: (property-drawer . org-org-identity)
|
| 3 matches for "property-drawer" in buffer: ox-texinfo.el
| 96: (property-drawer . org-texinfo-property-drawer)
| 1399:(defun org-texinfo-property-drawer (property-drawer contents info)
| 1400: "Transcode a PROPERTY-DRAWER element from Org to Texinfo.
`---------------------------------------------------------------------------
but in all cases (except ox-org.el) the function looks like this:
,---------------------------------------------------------------------
| (defun org-html-property-drawer (property-drawer contents info)
| "Transcode a PROPERTY-DRAWER element from Org to HTML.
| CONTENTS is nil. INFO is a plist holding contextual
| information."
| ;; The property drawer isn't exported but we want separating blank
| ;; lines nonetheless.
| "")
`---------------------------------------------------------------------
2. backends that don't (really) deal with property drawers:
,---------------------------------------------------------
| 1 match for "property-drawer" in buffer: ox-man.el
| 83: (property-drawer . (lambda (&rest args) ""))
|
| 1 match for "property-drawer" in buffer: ox-latex.el
| 70: (property-drawer . (lambda (&rest args) ""))
|
| ox-ascii.el: not found
| ox-icalendar.el: not found
| ox-md.el: not found
`---------------------------------------------------------
--
cheers,
Thorsten
next reply other threads:[~2013-06-17 9:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 9:53 Thorsten Jolitz [this message]
2013-06-17 14:33 ` [Feature Request] Make property-drawers exportable 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
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
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=8738shvzaj.fsf@gmail.com \
--to=tjolitz@gmail.com \
--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).