emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* setting export options in headline properties
@ 2021-07-21 18:52 Matt Price
  2021-07-21 20:25 ` Berry, Charles via General discussions about Org-mode.
  0 siblings, 1 reply; 3+ messages in thread
From: Matt Price @ 2021-07-21 18:52 UTC (permalink / raw)
  To: Org Mode

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

Hi,

I'm not sure if I'm reading the documentation properly, but my
understnading is that I ought to be able to set export options as subtree
properties, and that if I do so, they should be picked up by export engines
when exporting subtrees.  However, that doesn't see to be happening for me,
and from what I can tell, `org-export-get-environment` is not overriding
global values when passed the `subtreep` parameter.

I tried the following with emacs -Q , which seems to confirm my issue. Is
this the expected behaviour, and if so, is there some other way for me to
set subtree-level export options?

--------------
** subtree
:PROPERTIES:
:SUBTITLE: testing
:REVEAL_TITLE_SLIDE: nil
:HTML_CONTAINER: section
:END:


#+begin_src emacs-lisp
(let ((info (org-export-get-environment 'html t)))
  (string-join `(,(plist-get info :subtitle) ,(plist-get info
:html-container)) "\n")
  )
#+end_src

#+RESULTS:
:
: div
--------------------------

thanks as always!

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: setting export options in headline properties
  2021-07-21 18:52 setting export options in headline properties Matt Price
@ 2021-07-21 20:25 ` Berry, Charles via General discussions about Org-mode.
  2021-07-21 21:41   ` Matt Price
  0 siblings, 1 reply; 3+ messages in thread
From: Berry, Charles via General discussions about Org-mode. @ 2021-07-21 20:25 UTC (permalink / raw)
  To: Matt Price; +Cc: Org Mode

Matt,

Check (info "(org) Export Settings")

and especially, the para near bottom:

When exporting sub-trees, special node properties can override the
above keywords.  These properties have an ‘EXPORT_’ prefix.  For
example, ‘DATE’ becomes, ‘EXPORT_DATE’ when used for a specific
sub-tree.  Except for ‘SETUPFILE’, all other keywords listed above have
an ‘EXPORT_’ equivalent.

HTH,

Chuck

> On Jul 21, 2021, at 11:52 AM, Matt Price <moptop99@gmail.com> wrote:
> 
> Hi,
> 
> I'm not sure if I'm reading the documentation properly, but my understnading is that I ought to be able to set export options as subtree properties, and that if I do so, they should be picked up by export engines when exporting subtrees.  However, that doesn't see to be happening for me, and from what I can tell, `org-export-get-environment` is not overriding global values when passed the `subtreep` parameter.
> 
> I tried the following with emacs -Q , which seems to confirm my issue. Is this the expected behaviour, and if so, is there some other way for me to set subtree-level export options?
> 
> --------------
> ** subtree
> :PROPERTIES:
> :SUBTITLE: testing
> :REVEAL_TITLE_SLIDE: nil
> :HTML_CONTAINER: section
> :END:
> 
> 
> #+begin_src emacs-lisp 
> (let ((info (org-export-get-environment 'html t)))
>   (string-join `(,(plist-get info :subtitle) ,(plist-get info :html-container)) "\n")
>   )
> #+end_src
> 
> #+RESULTS:
> : 
> : div
> --------------------------
> 
> thanks as always!


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: setting export options in headline properties
  2021-07-21 20:25 ` Berry, Charles via General discussions about Org-mode.
@ 2021-07-21 21:41   ` Matt Price
  0 siblings, 0 replies; 3+ messages in thread
From: Matt Price @ 2021-07-21 21:41 UTC (permalink / raw)
  To: Berry, Charles; +Cc: Org Mode

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

arg.  thx, Chuck.

On Wed, Jul 21, 2021 at 4:25 PM Berry, Charles <ccberry@health.ucsd.edu>
wrote:

> Matt,
>
> Check (info "(org) Export Settings")
>
> and especially, the para near bottom:
>
> When exporting sub-trees, special node properties can override the
> above keywords.  These properties have an ‘EXPORT_’ prefix.  For
> example, ‘DATE’ becomes, ‘EXPORT_DATE’ when used for a specific
> sub-tree.  Except for ‘SETUPFILE’, all other keywords listed above have
> an ‘EXPORT_’ equivalent.
>
> HTH,
>
> Chuck
>
> > On Jul 21, 2021, at 11:52 AM, Matt Price <moptop99@gmail.com> wrote:
> >
> > Hi,
> >
> > I'm not sure if I'm reading the documentation properly, but my
> understnading is that I ought to be able to set export options as subtree
> properties, and that if I do so, they should be picked up by export engines
> when exporting subtrees.  However, that doesn't see to be happening for me,
> and from what I can tell, `org-export-get-environment` is not overriding
> global values when passed the `subtreep` parameter.
> >
> > I tried the following with emacs -Q , which seems to confirm my issue.
> Is this the expected behaviour, and if so, is there some other way for me
> to set subtree-level export options?
> >
> > --------------
> > ** subtree
> > :PROPERTIES:
> > :SUBTITLE: testing
> > :REVEAL_TITLE_SLIDE: nil
> > :HTML_CONTAINER: section
> > :END:
> >
> >
> > #+begin_src emacs-lisp
> > (let ((info (org-export-get-environment 'html t)))
> >   (string-join `(,(plist-get info :subtitle) ,(plist-get info
> :html-container)) "\n")
> >   )
> > #+end_src
> >
> > #+RESULTS:
> > :
> > : div
> > --------------------------
> >
> > thanks as always!
>
>

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-07-21 21:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-07-21 18:52 setting export options in headline properties Matt Price
2021-07-21 20:25 ` Berry, Charles via General discussions about Org-mode.
2021-07-21 21:41   ` Matt Price

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