From: Bastien <bzg@altern.org>
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Possible bug: List items with * in them when *:nil
Date: Mon, 30 Jan 2012 07:42:52 +0100 [thread overview]
Message-ID: <87obtld72f.fsf@altern.org> (raw)
In-Reply-To: <CAEWDx5fTu0RvNGiNSHz+V1eu+BvbPM+i+ONJL=Z8KMtwE8_L=w@mail.gmail.com> (Jonathan Leech-Pepin's message of "Sun, 29 Jan 2012 13:24:03 -0500")
Hi Jonathan,
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> The following sample org file does not export as possibly expected.
>
> ,-------------------------------------------
> | #+TITLE: Bug?
> | #+OPTIONS: *:nil toc:nil author:nil
> |
> | - hello (*) I would like to have two items
> | - may (*) I please?
> `-------------------------------------------
>
> Instead of the two items being listed with (*) as a part of their
> items they are placed on a single line as though they were still
> being
> wrapped in bold tags. I tested this further and it occurs in LaTeX,
> HTML and ODT exports. ASCII does the right thing and exports it as
> two list items.
The *:nil option is not the problem here.
The problem comes from the fact that the * in (*) actually _do_
emphasize the text (it is in bold font in the buffer). Given that, the
exporter does its best, which is not very good.
The bug here is to allow multiline fontification over distinct list
items -- we'll try to fix it, but that's a rather complex issue.
On top of the workaround above, have a look at
`org-emphasis-regexp-components', thru which you can prevent parentheses
as post/pre-characters in a fontified string.
HTH,
PS: FWIW, I also sent this reply to StackOverflow, thanks for
forwarding questions from there to here!
--
Bastien
prev parent reply other threads:[~2012-01-30 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 18:24 Possible bug: List items with * in them when *:nil Jonathan Leech-Pepin
2012-01-30 6:42 ` Bastien [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=87obtld72f.fsf@altern.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@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).