From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export of lists
Date: Wed, 24 Aug 2011 20:59:25 +0200 [thread overview]
Message-ID: <87boveoctu.fsf@gmail.com> (raw)
In-Reply-To: <m17h62zp2x.fsf@tsdye.com> (Thomas S. Dye's message of "Wed, 24 Aug 2011 07:39:18 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> I've just browsed the Document Structure chapter of the Org-mode manual:
> paragraphs aren't mentioned!
They are in "11.1 Structural markup elements"
> I'm not trying to be pedantic here and hold out for the presence or
> absence of blank lines to indicate a paragraph break in Org-mode. For
> the use case of lists set within a paragraph some other mechanism might
> be more appropriate.
I would suggest #+begin_latex #+end_latex for such specific needs
(paralist).
> But this circles back to the more general question of how paragraphs are
> indicated in Org-mode. Is it the blank line alone, or the blank line and
> other mechanisms?
There is no strict definition of a paragraph in Org core, yet. That's
why every exporter comes out with its own.
Though, a blank line is definitely seen as a paragraph break, as any
paragraph starter. So, what are these paragraph starters? Here are some:
- any line starting with #+, maybe indented. That includes keywords,
blocks, comments...
- fixed-width lines
- items
- headlines.
Now, defining a paragraph in Org wouldn't necessary be a bad thing for
exporters. This would just add information they could deliberately throw
away. That's why, again, keeping the exact number of blank lines is
important (for when they will throw the information away).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2011-08-24 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 16:16 LaTeX export of lists Thomas S. Dye
2011-07-24 16:44 ` Nick Dokos
2011-07-24 18:13 ` Nicolas Goaziou
2011-07-24 19:18 ` Thomas S. Dye
2011-07-25 8:45 ` Nicolas Goaziou
2011-07-25 16:15 ` Thomas S. Dye
2011-08-24 15:11 ` Eric S Fraga
2011-08-24 15:53 ` Nicolas Goaziou
2011-08-24 17:39 ` Thomas S. Dye
2011-08-24 18:59 ` Nicolas Goaziou [this message]
2011-08-24 19:45 ` Thomas S. Dye
2011-08-24 16:40 ` Achim Gratz
2011-08-24 17:08 ` Thomas S. Dye
-- strict thread matches above, loose matches on Subject: below --
2010-11-28 14:33 Thomas S. Dye
2010-11-28 15:05 ` Nicolas Goaziou
2010-11-28 18:40 ` Thomas S. Dye
2010-11-29 8:43 ` Sébastien Mengin
2010-11-27 22:02 Thomas S. Dye
2010-11-28 6:40 ` Richard Lawrence
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=87boveoctu.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).