emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Help with writing plain list followed by description list [ox-latex]
Date: Tue, 15 Mar 2016 23:25:54 -0400	[thread overview]
Message-ID: <CAFyQvY1zycKsrvrskE1WBxm_QE54stj96zZiqYFjkrPC5gDHFQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY2aUSwjxs1jhZ=XW0S50=383uVJXngEO5k+6foTafHKew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]

Ah, found the solution after I RTFM :)

*C-h i g (org) Plain lists*

"A list ends whenever every item has ended, which means before any
line less or equally indented than items at top level.  It also ends
before two blank lines(5)."


Here's the solution:

==============================================================
* Good (with 2 blank lines)
- Plain list item


- Description :: Description list became part of plain list here!
==============================================================



--
Kaushal Modi

On Tue, Mar 15, 2016 at 11:15 PM, Kaushal Modi <kaushal.modi@gmail.com>
wrote:

> Hi,
>
> I need help on generating a latex export correctly for the case where a
> description list has to immediately follow a plain list.
>
> Below is a MWE that demonstrates the problem and here is a screenshot of
> the generated PDF ( http://i.imgur.com/FEjN099.png ). Note how the
> Description list item looks under "Bad" section (generated using org) vs
> "Good" section (generated using latex code directly).
>
> ==============================================================
>
> * Bad
> - Plain list item
> - Description :: Description list became part of plain list here!
> -----
> Above does not work because org exports it to \LaTeX as below.
> #+BEGIN_EXAMPLE
> \section{Bad}
> \label{sec:orgheadline1}
> \begin{itemize}
> \item Plain list item
> \item[{Description}] Description list became part of plain list here!
> \end{itemize}
> #+END_EXAMPLE
> -----
> Note that the description list item comes *before* =\end{itemize}=.
>
> *How do I tell org to end the =itemize= block at the last plain list item
> and begin =description= block before the first description list item?*
>
> -- OR --
>
> *What should I write in org to generate the below?*
>
> -----
> #+BEGIN_EXPORT latex
> \section{Good}
> \label{sec:orgheadline2}
> \begin{itemize}
> \item Plain list item
> \end{itemize}
> \begin{description}
> \item[{Description}] This looks fine because I have moved the description
> list out of the plain list.
> \end{description}
> #+END_EXPORT
> -----
>
> ==============================================================
>
>
>
>
>
> --
> Kaushal Modi
>

[-- Attachment #2: Type: text/html, Size: 3464 bytes --]

      reply	other threads:[~2016-03-16  3:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16  3:15 Help with writing plain list followed by description list [ox-latex] Kaushal Modi
2016-03-16  3:25 ` Kaushal Modi [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=CAFyQvY1zycKsrvrskE1WBxm_QE54stj96zZiqYFjkrPC5gDHFQ@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).