From: Leo Butler <Leo.Butler@umanitoba.ca>
To: Ihor Radchenko <email@example.com>
Cc: Org Mode Mailing List <firstname.lastname@example.org>
Subject: Re: ox-beamer/latex questions
Date: Fri, 3 Mar 2023 17:46:48 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <87zg8t4zgo.fsf@localhost> (Ihor Radchenko's message of "Fri, 03 Mar 2023 15:38:31 +0000")
On Fri, Mar 03 2023, Ihor Radchenko <firstname.lastname@example.org> wrote:
> Leo Butler <Leo.Butler@umanitoba.ca> writes:
>>> This is because
>>> *** DONE :B_block:
>>> is actually parsed as a heading with DONE todo keyword and title
>>> ":B_block:". Tag is not recognized.
>>> We probably need to fix it, though I am not sure. It is one of the edge
>>> cases about Org parser.
>> Ok. I have become addicted to using TODO tags to organize composition of
>> beamer slides. I often have untitled blocks in the slides, in order to
>> control the pacing of the presentation.
> I understand. Just need to figure out the best way to alter the syntax.
> We should be careful with such things.
>>> For cookies, just use stat:nil in OPTIONS. See "13.2 Export Settings"
>>> section of the manual.
>> Thanks for that. I am not sure how I missed it.
>> Anyhow, it does not work correctly for subtree export (or I am not
>> understanding something). The title still includes the cookie. See the
> That was a rather interesting edge case that triggered a bug in
> Fixed, on main. It was a core function, so I did not risk bugfix.
next prev parent reply other threads:[~2023-03-03 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 21:37 ox-beamer/latex questions Leo Butler
2023-03-01 9:48 ` Ihor Radchenko
2023-03-01 19:16 ` Leo Butler
2023-03-01 21:11 ` Leo Butler
2023-03-03 15:38 ` Ihor Radchenko
2023-03-03 17:46 ` Leo Butler [this message]
2023-03-22 15:09 ` Ihor Radchenko
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).