[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] :EXPORT_FILE_NAME: in new exporter possible?
From: |
Nicolas Goaziou |
Subject: |
Re: [O] :EXPORT_FILE_NAME: in new exporter possible? |
Date: |
Fri, 22 Mar 2013 15:58:46 +0100 |
Hello,
Rainer Stengele <address@hidden> writes:
> Another funny issue here is that for the test my exported subtree has
> the tag :noexport:
>
> My setting is:
>
> org-export-exclude-tags is a variable defined in `ox.el'.
> Its value is ("noexport")
>
> So the export shouldn't export that subtree shouldn't it?
You're explicitly asking for a subtree export. There's no reason for the
export framework to think it is smarter than you and prevent you from
doing so.
When exporting a subtree, the parser only looks at the contents of the
top level headline, not at its tags.
Regards,
--
Nicolas Goaziou
- Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, (continued)
- Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, Bastien, 2013/03/25
- Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, Achim Gratz, 2013/03/25
- Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, Bastien, 2013/03/25
- Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, Bastien, 2013/03/25
- Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, Achim Gratz, 2013/03/25
Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, John Hendy, 2013/03/21
Re: [O] :EXPORT_FILE_NAME: in new exporter possible?,
Nicolas Goaziou <=
Re: [O] :EXPORT_FILE_NAME: in new exporter possible?, Rainer Stengele, 2013/03/22