From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Tags included in subtree export title despite tags:nil in header
Date: Thu, 27 Oct 2011 14:05:16 +0200 [thread overview]
Message-ID: <20111027140516.2f6d5508@kuru.homelinux.net> (raw)
In-Reply-To: <20111027134220.510ec38b@kuru.homelinux.net>
On Thu, 27 Oct 2011 13:42:20 +0200
Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> Hi Giovanni,
>
> On Thu, 27 Oct 2011 11:06:00 +0200
> Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> wrote:
>
> > suvayu ali <fatkasuvayu+linux@gmail.com> writes:
> >
> > Hi, Suvayu,
> > >
> > > I also have a subtree where I
> > > wrote beamer presentation about the project. I would like to
> > > exclude this from the html export, so I tag it with noexport.
> > >
> > > Now when I do a subtree export
> > ^^^^^^^^^^^^^^^^^
> > > to get the beamer presentation, my
> > > presentation has the title: "Text in headline :noexport:". Is
> > > there any way to exclude the tag from the exported title short of
> > > toggling the tag before export or setting the EXPORT_TITLE
> > > property?
> >
> > >
> > > I was expecting this to work out of the box since I already have
> > > tags:nil in the file header.
> > ^^^^^^^^^^^^^^^^^^^^
> > > Would this be considered as a bug?
> > I don't think so.
> >
> > Options for *the* specific subtree have to be defined in the
> > subtree:
> >
> > * file
> > ** beamer :noexport:
> > :PROPERTIES:
> > :EXPORT_TITLE: beamer
> > :EXPORT_FILE_NAME: test.html
> > :EXPORT_OPTIONS: H:3 num:nil toc:nil \n:t @:t ::t |:t ^:t f:nil *:t
> > tags:nil TeX:t LaTeX:nil skip:t p:nil author:nil email:nil
> > creator:nil timestamp:nil :END: beamer 2
> > *** beamer 3
> >
>
> As far as I know, the subtree inherits export and other options from
> the file header, e.g. ^:{}. I have that set in my file header, and
> subtree export respects that. That said, I tried your work around, I
> still get :noexport: in my title with the EXPORT_OPTIONS property set
> to tags:nil. I tried it with both latex and html export. Now I am
> pretty much convinced this is a genuine bug.
>
org-exp.el:2155:(defun org-export-get-title-from-subtree ()
This might be the guilty function. I don't see any checks for tags. I
don't understand the internals here. Maybe someone more well versed can
take a look?
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-10-27 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 18:20 Tags included in subtree export title despite tags:nil in header suvayu ali
2011-10-27 9:06 ` Giovanni Ridolfi
2011-10-27 11:42 ` Suvayu Ali
2011-10-27 12:05 ` Suvayu Ali [this message]
2011-10-29 13:08 ` Bastien
2011-10-29 14:48 ` Suvayu Ali
2011-10-29 16:13 ` Bastien
2011-10-29 23:10 ` Suvayu Ali
2011-10-30 1:07 ` Nick Dokos
2011-10-30 7:57 ` Suvayu Ali
2011-10-30 8:48 ` Bastien
2011-11-01 23:31 ` suvayu ali
2011-11-02 10:17 ` Bastien
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=20111027140516.2f6d5508@kuru.homelinux.net \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).