From: Ethan Ligon <ligon@are.berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Merge org-7.7 into emacs
Date: Sun, 7 Aug 2011 18:59:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20110807T204635-517@post.gmane.org> (raw)
In-Reply-To: 87hb5tun28.fsf@mean.albasani.net
Memnon Anon <gegendosenfleisch <at> googlemail.com> writes:
>
> Hi,
>
> Just a heads up:
>
> http://permalink.gmane.org/gmane.emacs.devel/142944
>
> I don't know anything about this, but maybe something can be said/done
> about it while Bastien enjoys his vacation?
>
I'm afraid I'm mentioned twice. The first has to do with copyright
assignment; I've begun the process described in org-contribute.org
to assign copyright to the FSF.
The second has to do with an incomplete ChangeLog entry for one of my
patches (commit 49e6bc899758114d6d29e69a8f9e40798d26782b). I don't
know the best to clean this up, since the ChangeLog is derived from
the git log. But here's a ChangeLog entry that I think would have been
valid:
commit 49e6bc899758114d6d29e69a8f9e40798d26782b
Author: Ethan Ligon <ligon@are.berkeley.edu>
Date: Sat Apr 9 18:39:35 2011 +0200
Fix for html & docbook export of description list items
* lisp/org-html.el (org-html-export-list-line): Fix regexp for
detecting description lists to allow "::" marker to be last
visible element at end of line.
* lisp/org-docbook.el (org-docbook-export-list-line): Fix regexp for
detecting description lists to allow "::" marker to be last
visible element at end of line.
The problem is illustrated by the following example:
* Illustration of bug in html export
- This has a space after the colons :: so will work in latex and html
- This doesn't have a space after the colons ::so is an invalid
description item according to the org manual. Won't work in html
or docbook. Will nevertheless work in latex, provided /first/
description item is valid.
- Has a terminating space ::
- So it works in both html and latex export!
- Even though it's difficult to distinguish from the next example.
- Lacks a terminating space ::
- At present, *doesn't* work in html or docbook export, does in
latex. This is the case that the following patch fixes.
-Ethan
next prev parent reply other threads:[~2011-08-07 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 17:54 Merge org-7.7 into emacs Memnon Anon
2011-08-07 18:40 ` suvayu ali
2011-08-09 12:26 ` Eric Schulte
2011-08-09 16:42 ` Memnon Anon
2011-08-15 13:57 ` Bastien
2011-08-15 14:03 ` Bastien
2011-08-15 14:04 ` suvayu ali
2011-08-07 18:59 ` Ethan Ligon [this message]
2011-08-15 14:35 ` Bastien
2011-08-15 14:39 ` Bastien
2011-08-27 15:31 ` Pieter Praet
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=loom.20110807T204635-517@post.gmane.org \
--to=ligon@are.berkeley.edu \
--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).