From: Thomas S. Dye <tsd@tsdye.com>
To: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Recent export bug?
Date: Mon, 10 May 2010 13:38:21 -1000 [thread overview]
Message-ID: <11B3CB27-DBAA-4868-BA02-D5F5D172A3E6@tsdye.com> (raw)
Aloha all,
The following minimal example doesn't export the Second heading to
html. The problem seems to be the :export: tag on the First heading.
If I remove the tag, then both the First and Second headings make it
into the export. I don't expect the :export: tag on the First heading
to stop export of the Second heading.
I found this behavior when I tried unsuccessfully to export an org
file that successfully exported last on April 6th. I don't believe
I've changed any html export settings in the meantime.
---------------
*
Setup
:noexport:
#+TITLE: export-tag.org
#+AUTHOR: Tom Dye
#+EMAIL: tsd@tsdye2.com
#+DATE: 2010-05-10 Mon
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:nil skip:nil d:nil todo:t pri:nil tags:not-in-
toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
*
First
:export:
Some First text
* Second
Some Second text
---------------
I tried to run git bisect, but if I go far enough back in time then I
run up against this:
eval-buffer: Symbol's function definition is void: org-overlay-put
This leaves me way over my head, but I did want you to know that I
worked a bit to isolate the problem and did my best to track it down
without success.
All the best,
Tom
next reply other threads:[~2010-05-10 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 23:38 Thomas S. Dye [this message]
2010-05-11 0:13 ` Recent export bug? Bernt Hansen
2010-05-11 0:57 ` Thomas S. Dye
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=11B3CB27-DBAA-4868-BA02-D5F5D172A3E6@tsdye.com \
--to=tsd@tsdye.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).