From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baoqiu Cui Subject: Re: {{{macro}}} expansion not working properly for docbook export Date: Wed, 20 May 2009 10:10:39 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M6pJh-0006rD-UN for emacs-orgmode@gnu.org; Wed, 20 May 2009 13:10:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M6pJd-0006op-TN for emacs-orgmode@gnu.org; Wed, 20 May 2009 13:10:57 -0400 Received: from [199.232.76.173] (port=52645 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M6pJd-0006oi-LK for emacs-orgmode@gnu.org; Wed, 20 May 2009 13:10:53 -0400 Received: from main.gmane.org ([80.91.229.2]:38565 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M6pJc-0000Tk-SD for emacs-orgmode@gnu.org; Wed, 20 May 2009 13:10:53 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M6pJb-0007MM-1w for emacs-orgmode@gnu.org; Wed, 20 May 2009 17:10:51 +0000 Received: from nat-dip4.cfw-a-gci.corp.yahoo.com ([209.131.62.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 May 2009 17:10:51 +0000 Received: from cbaoqiu by nat-dip4.cfw-a-gci.corp.yahoo.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 May 2009 17:10:51 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Dale Smith writes: > Baoqiu Cui writes: > >> Thanks for reporting this bug. For some reason I missed the coverage of >> macro support in DocBook exporter, and the bug was caused by an >> "optimization" that I thought I did in the code... Variable >> org-export-opt-plist should have been set but it was not in DocBook >> exporter. >> >> Attached please find the patch for the fix. Please let me know if it >> works. > > Works great! Thanks for the confirmation. > This bug may be related to another I noticed. I don't yet have a clear > picture yet of what is (not) going on. Basically, the time reported > by modification time was just plain wrong. By over a day. And I > *know* I just saved the file. > > I'm guessing now that the property was cached. If so, that property > should *not* be. It really needs to be fresh every time an export is > done. I am not able to reproduce this problem. I tried adding the following line in an Org file {{{modification-time(%Y-%m-%d %H:%M:%S)}}} and then tried to save the file multiple times with minor changes, and was able to consistently get the correct time in the exported DocBook file. Baoqiu