From: Bernt Hansen <bernt@norang.ca>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: information/feature request: org analog to latex \description environment
Date: Tue, 09 Sep 2008 17:04:02 -0400 [thread overview]
Message-ID: <87iqt5t4jh.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87od2xw1fj.fsf@gmail.com> (Eric Schulte's message of "Tue\, 09 Sep 2008 12\:42\:56 -0700")
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Does org currently support any syntax like the latex \desciption
> environment, something that would look like
>
> ,----
> | first: a description/definition of first
> | another: another item to be defined
> `----
>
> or
>
> ,----
> | - first: a description/definition of first
> | - another: another item to be defined
> `----
>
> in org, and would export to something like
>
> ,----
> | \begin{description}
> | \item[first] a description/definition of first
> | \item[another] another item to be defined
> | \end{description}
> `----
>
> in latex? If not would it be difficult/desirable to add?
>
> Thanks -- Eric
By default org export to latex creates description lists for headlines
when you go more than 3 levels deep.
Here's a sample org file where heading levels 2 and greater become
description lists.
,----[ play.org ]
| #+STARTUP:
| #+TITLE: play.org
| #+OPTIONS: H:1 num:t toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t TeX:t LaTeX:nil skip:nil d:nil tags:not-in-toc
| #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
| * Test file
| ** TODO Furniture
| *** TODO Chairs
| *** TODO Tables
| **** TODO Coffee Table
| Stuff goes here
| **** TODO Buffer Table
| More stuff goes here
`----
exorted with C-c C-e L
,----[ play.tex ]
| % Created 2008-09-09 Tue 17:00
| \documentclass[11pt,a4paper]{article}
| \usepackage[utf8]{inputenc}
| \usepackage[T1]{fontenc}
| \usepackage{hyperref}
|
|
| \title{play.org}
| \author{Bernt Hansen}
| \date{09 September 2008}
|
| \begin{document}
|
| \maketitle
|
| \section{Furniture}
|
| \begin{description}
|
| \item[Chairs]
|
|
| \end{description}
| \begin{description}
|
| \item[Tables]
|
|
| \begin{description}
|
| \item[Coffee Table]
|
|
| Stuff goes here
| \end{description}
| \begin{description}
|
| \item[Buffer Table]
|
|
| More stuff goes here
| \end{description}
| \end{description}
|
| \end{document}
`----
You can set the number of heading levels to export as headings in the
export options line (H:1)
-Bernt
next prev parent reply other threads:[~2008-09-09 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:42 information/feature request: org analog to latex \description environment Eric Schulte
2008-09-09 21:04 ` Bernt Hansen [this message]
[not found] ` <87zlmhgjnv.fsf@kassiopeya.MSHEIMNETZ>
[not found] ` <8763p5vz05.fsf@gmail.com>
2008-09-09 21:04 ` Sebastian Rose
2008-09-09 22:19 ` Eric Schulte
2008-09-10 6:46 ` Carsten Dominik
2008-09-21 7:22 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqt5t4jh.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.