From: Richard Stanton <stanton@haas.berkeley.edu>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: "nicholas.dokos@hp.com" <nicholas.dokos@hp.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Extra space between list items in HTML export
Date: Mon, 10 Sep 2012 16:39:18 -0700 [thread overview]
Message-ID: <CC73C7A7.245CE%stanton@haas.berkeley.edu> (raw)
In-Reply-To: <87pq5ta205.fsf@gmail.com>
On 9/10/12 4:31 PM, "Jambunathan K" <kjambunathan@gmail.com> wrote:
>
>>> From: nicholas.dokos@hp.com [mailto:nicholas.dokos@hp.com]
>>> Sent: Monday, September 10, 2012 2:37 PM
>>>
>>> > #+OPTIONS: h:2, toc:nil
>>> >
>>> > * Example of itemized list
>>> > ** Blank level 2 header
>>> > - List 1
>>> > - List 2
>>> > - List 3
>>> >
>>> > * Level 3 headings as itemized list, with extra space
>>> > ** Blank level 2 header
>>> > *** List 1
>>> > *** List 2
>>> > *** List 3
>>> >
>>>
>>> The old exporter does that: it breaks the second up into three lists,
>>>each with
>>> a single element. The first is a single list with three elements.
>>>
>>> The new exporter produces a single list with three elements, although
>>>it
>>> includes the section number for each entry - this might be a bug.
>>>
>>> Nick
>>
>> I also get the section number included as part of the list item
>> text. This does look like a bug.
>>
>> When I use the new exporter to export to LaTeX/PDF, I get no section
>> numbers, but I get a numbered, rather than itemized, list. This also
>> seems like a (different) bug.
>
>I have pushed a fix to org-e-html.el.
>
>The depth of numbering is according to the value of num:N spec. Use
> num:2 instead of num:t
>
>to get the numbering behaviour you desire.
>
>If something is not according to taste, point me to the markup that is
>missing or which needs to be removed (instead of describing it in
>English)
>
>> Richard
>>
>>
>
>--
Thanks. I'll try the new version.
Meanwhile, as I understand it (and as implemented in the old exporter),
h:2 should mean that only two levels of section headings should be created
at all. Level 3 should be an itemized list (and therefore, implicitly,
should not have a number). Thus, h:2 should imply n:2, I believe.
next prev parent reply other threads:[~2012-09-10 23:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 21:23 Extra space between list items in HTML export Richard Stanton
2012-09-10 21:37 ` Nick Dokos
2012-09-10 22:39 ` Richard Stanton
2012-09-10 23:31 ` Jambunathan K
2012-09-10 23:39 ` Richard Stanton [this message]
2012-09-10 23:45 ` Jambunathan K
2012-09-10 23:47 ` Richard Stanton
2012-09-11 0:52 ` Nick Dokos
2012-09-11 7:30 ` Jambunathan K
2012-09-11 8:00 ` Nick Dokos
2012-09-18 7:26 ` Bastien
2012-09-18 14:34 ` Bastien
2012-09-18 13:26 ` Bastien
2012-09-18 16:13 ` Richard Stanton
2012-09-19 6:53 ` Bastien
2012-09-19 16:01 ` Richard Stanton
2012-09-19 16:45 ` Bastien
2012-09-19 20:55 ` Richard Stanton
2012-09-18 13:25 ` Bastien
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=CC73C7A7.245CE%stanton@haas.berkeley.edu \
--to=stanton@haas.berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=nicholas.dokos@hp.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).