Eden Cardim <edencar...@gmail.com> wrote: > > ,----[ test.org ] > | #+OPTIONS: <:nil > | ** TODO Estimate effort for all of today's tasks > | SCHEDULED: <2011-05-05 Thu 06:40 ++1d> > `---- > > Exporting the above file to pdf results in a file containing the > SCHEDULED timestamp in it. > > I'm running org from git master, commit > cd0446243861487096983f09e545105551af7f10 > > Apparently, all the symbol settings (^:t |:t etc...) exhibit the same > behaviour. Options like toc:t, num:t, etc. do work. I'm not familiar > with the code that does the parsing of the options so I have no idea > where to look in order to debug this. Setting org-export-with-timestamps > etc. does work as documented, so I'd say something is going wrong with > the parsing. >
Reproduced and git bisected: ,---- | aa6dba8a74016587755c250bb8cc4743a4082ea1 is the first bad commit | commit aa6dba8a74016587755c250bb8cc4743a4082ea1 | Author: Lawrence Mitchell <we...@gmx.li> | Date: Thu Jan 20 18:23:22 2011 +0000 | | Only match complete words in org-export-add-options-to-plist | | * org-exp.el (org-export-add-options-to-plist): Require match to start | at a word-boundary. | | Previously, if an option was the suffix of another option (such as TeX | and LaTeX) the setting for the former would propagator to the latter. | This seems like an unintended consequence of a lax regexp in | org-export-add-options-to-plist. This patch allows options to share a | suffix with another option by requiring that the match against an | option starts at a word-boundary. | | :040000 040000 44d426100f5c092112e149a891eb2e043a8ca404 c76627facb6988aa08d4d1fa9f1ab2d9b4aa2f45 M lisp `---- Lawrence, can you take a look? Thanks, Nick