From: David Maus <dmaus@ictsoc.de>
To: Daniel Clemente <n142857@gmail.com>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Re: can't export custom time stamps
Date: Sun, 13 Mar 2011 20:49:20 +0100 [thread overview]
Message-ID: <87sjuqhkcf.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <87d3lydnv3.wl%n142857@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
At Fri, 11 Mar 2011 10:10:08 +0100,
Daniel Clemente wrote:
>
>
> I tracked down this problem to this commit:
>
>
> 163cd58ffd6461c98a96b1b63a3cf082b2825a52 is the first bad commit
> commit 163cd58ffd6461c98a96b1b63a3cf082b2825a52
> Author: David Maus <dmaus@ictsoc.de>
> Date: Fri Jan 14 06:37:52 2011 +0100
>
> Handle timestamps after handling links
Thanks for tracking this down. I just pushed two commits that should
fix the problem.
The first reverts
commit ca69b556241ae904c5f291c98a6453f4ce830557
Author: Jason Dunsmore <emacs-orgmode@dunsmor.com>
Date: Tue Feb 1 17:46:57 2011 +0100
Fix bug when exporing inactive timestamps.
* org-html.el (org-html-handle-time-stamps): fix bug when
exporing inactive timestamps.
This commit addressed the problem introduced by
163cd58ffd6461c98a96b1b63a3cf082b2825a52 but in a way that is
incompatible with the "right" fix.
My faulty commit not just changed the order of handling links and
handling timestamps but also prevented the left angle bracket of an
active timestamp from beeing protected from conversion to a HTML
character entity (i.e. <).
The (hopefully) final fix moves expanding character entities after
handling links and timestamps.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-03-13 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 20:19 can't export custom time stamps Daniel Clemente
2011-03-11 9:10 ` Daniel Clemente
2011-03-13 19:49 ` David Maus [this message]
2011-03-14 6:02 ` Daniel Clemente
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=87sjuqhkcf.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@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).