From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Martin Steffen <msteffen@ifi.uio.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: org export customization: why do #+EXCLUDE_TAGS: settings have no effect?
Date: Wed, 11 Nov 2015 22:06:19 +0100 [thread overview]
Message-ID: <871tbw8cvo.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <xk92oaf1ovlx.fsf@nittedal.ifi.uio.no> (Martin Steffen's message of "Wed, 11 Nov 2015 08:15:06 +0100")
Martin Steffen <msteffen@ifi.uio.no> writes:
> For your small example (exporting to latex) I get
>
> \begin{itemize}
> \item H1 :private:
> \item H2
> \end{itemize}
Then something may be wrong with `org-export-headline-levels', or
`org-latex-classes' in your config.
> What is strange though: the emacs-variable org-export-headline-levels
> does not change when doing that, expect that I would have expected that
> refreshing the buffer would do exactly that: update that variable and
> thereby influencing the sectioning-levels:
>
> ---------------------
> org-export-headline-levels is a variable defined in `ox.el'.
> Its value is 3
> ...
> This option can also be set with the OPTIONS keyword,
> e.g. "H:2".
> ---------------------
ox-beamer uses this option item for something else,
`org-beamer-frame-level'. IOW `org-export-headline-levels' has no effect
during Beamer export.
> I did not to comprehensive experiments which #+OPTIONS work or work
> strangely, I just noticed that H:3 etc ``work'' (but I don't know why),
> whereas the #EXCLUDE_TAGS do ``not work'' when refreshing the
> buffer. For instance in that simple example you provided.
Did you try with emacs -Q?
Regards,
prev parent reply other threads:[~2015-11-11 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 18:47 org export customization: why do #+EXCLUDE_TAGS: settings have no effect? Martin Steffen
2015-11-10 22:44 ` Nicolas Goaziou
2015-11-11 7:15 ` Martin Steffen
2015-11-11 21:06 ` Nicolas Goaziou [this message]
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=871tbw8cvo.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=msteffen@ifi.uio.no \
/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).