From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Pattern of global/file/headings variables/settings
Date: Wed, 25 Sep 2013 14:56:27 +0200 [thread overview]
Message-ID: <2013-09-25T14-40-50@devnull.Karl-Voit.at> (raw)
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
next reply other threads:[~2013-09-25 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 12:56 Karl Voit [this message]
2013-09-25 14:10 ` Pattern of global/file/headings variables/settings 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2013-09-25T14-40-50@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.