From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Fwd: Export to Texinfo
Date: Fri, 3 Aug 2012 09:30:02 -0400 [thread overview]
Message-ID: <CAHRqSkT0iyGmczj_Eob=JyMNnh_=-QuTwsHPTNFGaSgPaHb0Sg@mail.gmail.com> (raw)
In-Reply-To: <87a9yccqqr.fsf@gmail.com>
Hello,
On Fri, Aug 3, 2012 at 4:41 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
>> Nested lists do work with only a small issue I can see at the moment,
>> if there are no blank lines between the items in org there are none in
>> the info file either, however there are 2 blank lines at the end of
>> the nested list (end of nested list+end of parent item).
>
> By default, Org export preserves the number of blank lines during
> conversion. If no blank line separates two elements in the Org buffer,
> no blank line will separate their transcoded version.
>
> You can change this by using filters. For example "md" back-end
> enforces at least one blank line between elements (see
> `org-md-separate-elements') and "e-ascii" back-end normalizes the number
> of blank lines after an headline (see
> `org-e-ascii-filter-headline-blank-lines').
>
> Filters are installed by :filters-alist keyword in
> `org-export-define-backend' and `org-export-define-derived-backend'.
>
I thought I'd set it to normalize (set a filter similar to the
one in org-e-ascii), but I must have gotten some part not quite
right. I'll look it over again.
>> When I export the attached .org file the only difference I get from
>> your .texi is the AUTHOR and the chapter/sections are numbered rather
>> than unnumbered (and the level 4 headline is an enumerate rather than
>> an itemize).
>
> Ideally, for "listified" headlines, list type (ordered or not) should be
> determined by `org-export-numbered-headline-p' predicate.
>
They do follow the numbered/unnumbered settings. When I exported
every headline (listified or otherwise) was numbered, in
Bastien's example they were all unnumbered, so it was consistent.
>
> Regards,
>
> --
> Nicolas Goaziou
Regards,
--
Jon
prev parent reply other threads:[~2012-08-03 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 0:29 Export to Texinfo Jonathan Leech-Pepin
2012-07-20 9:32 ` Nicolas Goaziou
2012-07-20 13:34 ` Jonathan Leech-Pepin
2012-07-20 13:42 ` Nicolas Goaziou
2012-07-31 21:03 ` Jonathan Leech-Pepin
2012-07-31 21:18 ` Nicolas Goaziou
2012-07-31 22:35 ` Jonathan Leech-Pepin
2012-07-31 23:45 ` Jonathan Leech-Pepin
2012-08-02 15:34 ` Bastien
[not found] ` <CAHRqSkQTzE-OYmTFs+BRjrER=jgS3=2BE5Yi4A6v8ipaZ1kWQA@mail.gmail.com>
2012-08-02 22:24 ` Fwd: " Jonathan Leech-Pepin
2012-08-03 7:29 ` Bastien
2012-08-03 8:41 ` Nicolas Goaziou
2012-08-03 13:30 ` Jonathan Leech-Pepin [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='CAHRqSkT0iyGmczj_Eob=JyMNnh_=-QuTwsHPTNFGaSgPaHb0Sg@mail.gmail.com' \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).