emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dale Smith <dsmith@vtiinstruments.com>
To: Baoqiu Cui <cbaoqiu@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Re: {{{macro}}} expansion not working properly for docbook export
Date: Wed, 20 May 2009 14:23:38 -0400	[thread overview]
Message-ID: <kpws8bvdjp.fsf@flexo.cle.vtiinstruments.lcl> (raw)
In-Reply-To: <bycab5766pc.fsf@muchbodyking-lm.corp.yahoo.com> (Baoqiu Cui's message of "Wed, 20 May 2009 12:10:39 -0500")

Baoqiu Cui <cbaoqiu@yahoo.com> writes:

>> 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.

Indeed is *is* now working correctly.  So I guessing that the time was
"frozen" at the point I did an html export.  Now that the docbook
exporter is generating the properties, the time is being updated.
Yay!

Thanks again,
  -Dale

-- 
Dale P. Smith
dales@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif

      reply	other threads:[~2009-05-20 19:04 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
2009-05-20 18:23       ` Dale Smith [this message]

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=kpws8bvdjp.fsf@flexo.cle.vtiinstruments.lcl \
    --to=dsmith@vtiinstruments.com \
    --cc=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).