From: Haojun Bao <baohaojun@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug(?) ox-html always add a timestamp in comment which can't be customized away
Date: Sat, 8 Jun 2013 13:46:55 +0800 [thread overview]
Message-ID: <CAABrf9a=sxSxYcaCtODYv1KUw6iyiQAoMuFbR4825uQ=V=rmMQ@mail.gmail.com> (raw)
In-Reply-To: <87ehcdkw3g.fsf@pierrot.dokosmarshall.org>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Just checked, it is the same tag (release_8.0.3), there is no change like
in your code.
Could you please run git blame on those lines?
On Sat, Jun 8, 2013 at 1:30 PM, Nick Dokos <ndokos@gmail.com> wrote:
> Haojun Bao <baohaojun@gmail.com> writes:
>
> > The culprit code is the following:
> >
> > (when :time-stamp-file
> > (format-time-string
> > (concat "<!-- " org-html-metadata-timestamp-format " -->\n")))
> >
> > This `when' condition is always true, because :time-stamp-file is a
> > keyword and always eval to itself, never to nil.
> >
> > So I think org-export-time-stamp-file should be used instead of
> > :time-stamp-file.
> >
>
> What version are you using? In the version I have, the code looks like
> this:
>
> (when (plist-get info :time-stamp-file)
> (format-time-string
> (concat "<!-- " org-html-metadata-timestamp-format " -->\n")))
>
> Org-mode version 8.0.3 (release_8.0.3-197-g221768)
> [nb: this version includes a few local commits (irrelevant to this
> subject)]
> --
> Nick
>
>
>
[-- Attachment #2: Type: text/html, Size: 1685 bytes --]
next prev parent reply other threads:[~2013-06-08 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 5:22 bug(?) ox-html always add a timestamp in comment which can't be customized away Haojun Bao
2013-06-08 5:30 ` Nick Dokos
2013-06-08 5:46 ` Haojun Bao [this message]
2013-06-08 6:04 ` Nick Dokos
2013-06-08 14:14 ` Haojun Bao
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='CAABrf9a=sxSxYcaCtODYv1KUw6iyiQAoMuFbR4825uQ=V=rmMQ@mail.gmail.com' \
--to=baohaojun@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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).