* Pattern of global/file/headings variables/settings
@ 2013-09-25 12:56 Karl Voit
2013-09-25 14:10 ` Thorsten Jolitz
0 siblings, 1 reply; 2+ messages in thread
From: Karl Voit @ 2013-09-25 12:56 UTC (permalink / raw)
To: emacs-orgmode
Hi!
I wonder how Org-mode turned out as it is with regard to settings
that could be done in .emacs (user), as file-local ones (file), or
with properties (heading).
As an example:
[1] mentions:
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [bigger]
#+BEAMER_FRAME_LEVEL: 2
I could find "EXPORT_LATEX_CLASS" and "EXPORT_LATEX_CLASS_OPTIONS"
using full-text search in [2]. However, I was not able to locate any
property which relates to #+BEAMER_FRAME_LEVEL, e.g.
So: what is the pattern here? Which setting goes to setq (user),
#+FOO (file), :PROPERTY: (heading)?
I assume that every additional possibility (of the three) relates to
manual effort to be implemented. Right?
If not: why can't there be a general pattern where a user can assume
that #+foo (file) can be applied as :FOO: (heading) as well?
Background: I do not want to create a whole new Org-mode file for
just one single beamer presentation. I love it when I can keep *all*
relevant data within its project heading, wherever that might be
located in my (few) Org-mode files. Thus, as a sub-heading of
business.org > projects > customerA > reports > final-report I want
to add my beamer presentation data as well.
Thanks for clarifying!
1. http://orgmode.org/worg/exporters/beamer/tutorial.html
2. http://orgmode.org/org.html
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Pattern of global/file/headings variables/settings
2013-09-25 12:56 Pattern of global/file/headings variables/settings Karl Voit
@ 2013-09-25 14:10 ` Thorsten Jolitz
0 siblings, 0 replies; 2+ messages in thread
From: Thorsten Jolitz @ 2013-09-25 14:10 UTC (permalink / raw)
To: emacs-orgmode
Karl Voit <devnull@Karl-Voit.at> writes:
Hi,
> I wonder how Org-mode turned out as it is with regard to settings
> If not: why can't there be a general pattern where a user can assume
> that #+foo (file) can be applied as :FOO: (heading) as well?
and I wonder why
,----------------------
| #+ATTR_HTML: :foo bar
`----------------------
on top of a table becomes a ':attr_html' attribute of the table 's
property list, but the same thing on top of a headline becomes a
(keyword ...) that belongs to the section preceding the headline - when
parsing the buffer with `org-element-parse-buffer'.
I would have expected that all affiliated keywords with the pattern
,----------------------
| #+ATTR_<<backend>>: :foo bar
`----------------------
directly on top of an element are converted to attributes of the element
they are attached to, no matter what <<backend>> actually looks like
(or, at least, when <<backend>> is listed in `org-export-backends' or
`org-export--registered-backends' or so).
--
cheers,
Thorsten
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-09-25 14:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-25 12:56 Pattern of global/file/headings variables/settings Karl Voit
2013-09-25 14:10 ` Thorsten Jolitz
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).