From: Jambunathan K <kjambunathan@gmail.com>
To: Tim <wiskey5alpha@gmail.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Carriage return in macro
Date: Sat, 31 Aug 2013 12:11:13 +0530 [thread overview]
Message-ID: <87d2ous6pi.fsf@gmail.com> (raw)
In-Reply-To: <87eh9bigkq.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 30 Aug 2013 16:35:57 +0530")
Nicolas
In the context of the example below (i.e., the way #+ATTR_ODT are used
/within/ the list) is it fair to say this:
A #+ATTR_ODT: can be attached only to a plain-list - Visually they
come before the first item of the top-level list or a nested list.
Using an #+ATTR_ODT line before a second or subsequent item will
result in splitting of the original list.
I just want to confirm my understanding of the /existing/ behaviour so
that I can extract maximum juice out of ox.el.
To avoid confusion: Opinions surrounding how comments and meta lines
influence the list structure doesn't bother me one way or the other.
Jambunathan K <kjambunathan@gmail.com> writes:
> #+ATTR_ODT: :style "OrgBulletedList" :p-style "Text_20_body_20_bold"
> 1. N1
> 1. N11
> 2. N12
> 2. N2
> #+ATTR_ODT: :style "OrgNumberedList" :p-style "Preformatted_20_Text"
> * B21
>
> * B22
> - B221
>
> First paragraph.
>
> #+ATTR_ODT: :style "OrgBibliographyList" :p-style "Text_20_body"
> 1. one
> 2. two
> 3. three
>
> #+ATTR_ODT: :style "Text_20_body_20_indent"
> Second paragraph.
>
> - B222
> * B23
> 3. N3
next prev parent reply other threads:[~2013-08-31 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 20:04 Carriage return in macro Timothy Aldrich
2013-08-26 10:16 ` Nicolas Goaziou
2013-08-27 17:40 ` Tim
2013-08-27 19:06 ` Nicolas Goaziou
2013-08-30 11:05 ` Jambunathan K
2013-08-31 6:41 ` Jambunathan K [this message]
2013-08-31 12:38 ` Nicolas Goaziou
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=87d2ous6pi.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=wiskey5alpha@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).