From: Suvayu Ali <email@example.com>
Cc: Bastien <firstname.lastname@example.org>, org-mode mailing list <email@example.com>
Subject: Re: Tags included in subtree export title despite tags:nil in header
Date: Sun, 30 Oct 2011 08:57:22 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Sat, 29 Oct 2011 21:07:27 -0400
Nick Dokos <email@example.com> wrote:
> Suvayu Ali <firstname.lastname@example.org> wrote:
> > In the attached patch, I use the variable org-export-with-tags to
> > check whether tags should be included or skipped in the export
> > title. However irrespective of the export options I get the value
> > not-in-toc. As a result, the tags are not included even if tags:t
> > is set.
> > Is my use of org-export-with-tags incorrect? Is there something
> > else I need to do before I can use it?
> Try changing the test to just
> + (setq title (if org-export-with-tags
> + (format "%s\t%s" (match-string 3)
> (match-string 4))
> + (match-string 3)))
> This checks whether org-export-with-tags is non-nil, rather than
> checking that it is exactly t. In general, checking for nil or
> non-nil is probably a better way to go, unless there are specific
> reasons to be more specific.
That was my original attempt. But I went with the eq test since I
thought tags:not-in-toc would also imply the user doesn't want the tags
to be included in the export title.
That said, the problem I am facing is org-export-with-tags evaluates to
not-in-toc irrespective of what is set by the tags: option (see for
example the test file earlier in the thread). So effectively the test
is not checking what it is supposed to check. So I was wondering
whether I missed something I should be doing.
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-10-30 7:57 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
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 [this message]
2011-10-30 8:48 ` Bastien
2011-11-01 23:31 ` suvayu ali
2011-11-02 10:17 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).