emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Parsing property drawers in subtree scope exports
Date: Sat, 01 Jul 2017 18:08:06 +0200	[thread overview]
Message-ID: <87injc2l95.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY2pvkActtg_2URijppbyN_eUvxCm=wQvKLT=t=5M+nRZQ@mail.gmail.com> (Kaushal Modi's message of "Sat, 01 Jul 2017 13:09:37 +0000")

Kaushal Modi <kaushal.modi@gmail.com> writes:

> I didn't follow that. Do you mean that the "EXPORT_" is a special
> prefix?

I do. See (info "(org) Export settings").

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

If you set this, you can access to EXPORT_HUgo_TAGS property
with :hugo-tags.

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

(plist-get info :hugo-tags)

> 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?

You can also do that, if you don't use the "EXPORT_" prefix above.
However, you need to expand the buffer first, because it will be
narrowed to the current subtree.

Regards,

  reply	other threads:[~2017-07-01 16:08 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
2017-07-01 16:08     ` Nicolas Goaziou [this message]
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=87injc2l95.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@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).