emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Parsing property drawers in subtree scope exports
Date: Sat, 01 Jul 2017 13:09:37 +0000	[thread overview]
Message-ID: <CAFyQvY2pvkActtg_2URijppbyN_eUvxCm=wQvKLT=t=5M+nRZQ@mail.gmail.com> (raw)
In-Reply-To: <87y3s84mxp.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

Hello,

On Sat, Jul 1, 2017, 3:48 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:

>
> You can write it :EXPORT_FOO: and define it in the back-end options.
>

I didn't follow that. Do you mean that the "EXPORT_" is a special prefix?
Or "EXPORT" is any backend prefix I choose?

Should that be added to these?

=====
:options-alist '((:hugo-front-matter-format "HUGO_FRONT_MATTER_FORMAT" nil
org-hugo-front-matter-format)
(:hugo-tags "HUGO_TAGS" nil nil)
=====

I already tried above, but I don't know how to get the ":HUGO_TAGS" value
from the property drawer, in subtreep export only, in the body filter (with
only body and info available).

If it is a full document export, I can use the "org export parse headlines"
function (forgot the name, on the phone at the moment) to get the
properties from each headline. But the same doesn't work when exporting
just one sub-tree.

Otherwise, you simply need to retrieve it and store it before calling
> `org-export-to-file' or whatever.


Hmm, will give this a try.. may be look at the pre export hook?

Thank you.
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1916 bytes --]

next prev parent reply	other threads:[~2017-07-01 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01  6:58 Parsing property drawers in subtree scope exports Kaushal Modi
2017-07-01  7:48 ` Nicolas Goaziou
2017-07-01 13:09   ` Kaushal Modi [this message]
2017-07-01 16:08     ` Nicolas Goaziou
2017-07-06 17:08       ` Kaushal Modi
2017-07-06 17:19         ` Nicolas Goaziou

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='CAFyQvY2pvkActtg_2URijppbyN_eUvxCm=wQvKLT=t=5M+nRZQ@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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).