* org export customization: why do #+EXCLUDE_TAGS: settings have no effect?
@ 2015-11-09 18:47 Martin Steffen
2015-11-10 22:44 ` Nicolas Goaziou
0 siblings, 1 reply; 4+ messages in thread
From: Martin Steffen @ 2015-11-09 18:47 UTC (permalink / raw)
To: emacs-orgmode
Hi,
I want selective export in org (for instance, exporting to beamer/latex, and
html etc). I seem to understand the "theory" but it seems not really to work
for me.
what _works_ is as follows: I set directly a corresponding variable, in
particular, for instance, set it "hard" to
(setq org-export-exclude-tags '("noexport" "private" "handout")
"noexport" is the original value, but I want to keep trees tagged as
"private" and as "handout" out of for instance the slides.
Now that seems to work.
Now: when I want to /customize/ that in the org-file itself, it seems that's
done by doing something like
#+EXCLUDE_TAGS: private
(In (older?) versions, I also found #+EXPORT_EXCLUDE_TAGS).
Anyhow: having such a specification in the org-file seems to have /no
effect/, even if I "refresh" the org-file, nor does it work when I visit the
file for the first time. It seems simply not to affect the said variable
"org-export-exclude-tags"
--
I use a pretty up-to-date org version pulled from git-hub (org-version
8.3.2, emacs-version 24.3.1)
Martin
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: org export customization: why do #+EXCLUDE_TAGS: settings have no effect?
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
0 siblings, 1 reply; 4+ messages in thread
From: Nicolas Goaziou @ 2015-11-10 22:44 UTC (permalink / raw)
To: Martin Steffen; +Cc: emacs-orgmode
Hello,
Martin Steffen <msteffen@ifi.uio.no> writes:
> Now: when I want to /customize/ that in the org-file itself, it seems that's
> done by doing something like
>
>
> #+EXCLUDE_TAGS: private
[...]
> Anyhow: having such a specification in the org-file seems to have /no
> effect/, even if I "refresh" the org-file, nor does it work when I visit the
> file for the first time. It seems simply not to affect the said variable
> "org-export-exclude-tags"
I cannot reproduce your issue. With the following buffer
#+EXCLUDE_TAGS: private
* H1 :private:
* H2
I get
1 H2
════
when I export to, e.g., UTF-8.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: org export customization: why do #+EXCLUDE_TAGS: settings have no effect?
2015-11-10 22:44 ` Nicolas Goaziou
@ 2015-11-11 7:15 ` Martin Steffen
2015-11-11 21:06 ` Nicolas Goaziou
0 siblings, 1 reply; 4+ messages in thread
From: Martin Steffen @ 2015-11-11 7:15 UTC (permalink / raw)
To: emacs-orgmode
Thanks,
For your small example (exporting to latex) I get
\begin{itemize}
\item H1 :private:
\item H2
\end{itemize}
(apart from the preamble etc). What is also weird: If I add the
``standard'' vanilla template (via C-c C-e # beamer), then
- 1) some option settings like H:2 vs H:3 /are/ working.
- 2) variable org-export-headline-levels does not change
By "working" I mean: if I change the #+OPTIONS: H:2 to H:3, refresh the
emacs-buffer wrt. org's settings, and export the output (concretetely I
did beamer/latex). Now changing the section-level head /does change/ the
beamer-latex output the way I'd expect (i.e., it influences the
sectioning level).
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".
---------------------
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.
Martin
>>>>> "Nicolas" == Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
Nicolas> Hello,
Nicolas> Martin Steffen <msteffen@ifi.uio.no> writes:
>> Now: when I want to /customize/ that in the org-file itself, it
>> seems that's done by doing something like
>>
>>
>> #+EXCLUDE_TAGS: private
Nicolas> [...]
>> Anyhow: having such a specification in the org-file seems to have
>> /no effect/, even if I "refresh" the org-file, nor does it work
>> when I visit the file for the first time. It seems simply not to
>> affect the said variable "org-export-exclude-tags"
Nicolas> I cannot reproduce your issue. With the following buffer
Nicolas> #+EXCLUDE_TAGS: private * H1 :private: * H2
Nicolas> I get
Nicolas> 1 H2 ════
Nicolas> when I export to, e.g., UTF-8.
Nicolas> Regards,
Nicolas> -- Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: org export customization: why do #+EXCLUDE_TAGS: settings have no effect?
2015-11-11 7:15 ` Martin Steffen
@ 2015-11-11 21:06 ` Nicolas Goaziou
0 siblings, 0 replies; 4+ messages in thread
From: Nicolas Goaziou @ 2015-11-11 21:06 UTC (permalink / raw)
To: Martin Steffen; +Cc: emacs-orgmode
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,
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-11-11 21:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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).