emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Baoqiu Cui <cbaoqiu@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: {{{macro}}} expansion not working properly for docbook export
Date: Wed, 20 May 2009 10:10:39 -0700	[thread overview]
Message-ID: <bycab5766pc.fsf@muchbodyking-lm.corp.yahoo.com> (raw)
In-Reply-To: kpbppnx3sp.fsf@flexo.cle.vtiinstruments.lcl

Dale Smith <dsmith@vtiinstruments.com> writes:

> Baoqiu Cui <cbaoqiu@yahoo.com> 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

  reply	other threads:[~2009-05-20 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 14:59 {{{macro}}} expansion not working properly for docbook export Dale Smith
2009-05-20  7:11 ` Baoqiu Cui
2009-05-20 14:11   ` Dale Smith
2009-05-20 17:10     ` Baoqiu Cui [this message]
2009-05-20 18:23       ` Dale Smith

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=bycab5766pc.fsf@muchbodyking-lm.corp.yahoo.com \
    --to=cbaoqiu@yahoo.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).