emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marius Hofert <marius.hofert@math.ethz.ch>
To: nicholas.dokos@hp.com
Cc: Emacs help <emacs-orgmode@gnu.org>
Subject: Re: How to get numbered lists (1), (2), … ?
Date: Thu, 13 Oct 2011 22:00:36 +0200	[thread overview]
Message-ID: <3414CE30-6774-4566-9391-D6929BDC4C87@math.ethz.ch> (raw)
In-Reply-To: <5133.1318533018@alphaville.americas.hpqcorp.net>

Dear Nick,

thanks for helping. 

What do you mean by "better solution"? As far as I can tell, your approach is precisely what Suvayu pointed to. Using your approach, of course much more is possible, please look at the create "enumitem" package with all its customizations. 

But this approach is a no-go for me (at least at the moment) mainly due to the following reasons (please let me know if I'm wrong, I'm a total newbie to org-mode):
1) I have about 40 lists in one file. Having to put in special LaTeX commands is not an option (maybe on only has to type it in once, but then it can easily get overseen, e.g., when you move lists around and the one containing the LaTeX commands is not the first one in the document anymore)
2) org-mode is basically a "better" text-mode. I don't want to have LaTeX code in there if I print it as a .txt file.

Is there a solution without having to put
#+LATEX_HEADER: \usepackage{enumerate}
before each list? Can this be set anywhere in the preferences? 

But I assume that I still have to put in lists in org-mode like this: 1.,2.,... or 1),2),... and can't put them in like this (1),(2),...?
Hmm... this is indeed a drawback. The latter lists a far better visible, they are more consistent with respect to other list types such as (i), (ii), etc., and ultimately also with respect to numbering of equations. There are probably even more typographic reasons to display lists like this. For example, if you refer to a list within a theorem environment (which has a label itself) and you use 1., 2.,... lists, then this looks like this:
Theorem 1.2 2. shows that ...
The eye hardly sees that one means Theorem 1.2 Part (2). Even worse, when reading this, one thinks that the sentence stops after "2.". It's really a bad thing, and not getting much better with right-sided parentheses. 

Cheers,

Marius

On 2011-10-13, at 21:10 , Nick Dokos wrote:

> 
> [ I started this earlier but I guess I didn't send it out. Suvayu has
>  replied in the meantime with a pointer to a better solution than this
>  one, but this might be of some minor interest to some people as well -
>  besides, I spent a whole 20 minutes on it, half of it trying to figure
>  out why my mail was not working :-( : why let that effort go to
>  waste?:-) ]
> 
> 
> Marius Hofert <marius.hofert@math.ethz.ch> wrote:
> 
>> Dear Suvayu,
>> 
>> thanks. 
>> It would be good to know how latex export can be customized to achieve this.
>> 
> 
> Depends on how much customization you are willing to go through: there is an
> enumerate.sty package in LaTeX that can do that:
> 
> --8<---------------cut here---------------start------------->8---
> ...
> \usepackage{enumerate}
> ...
> \begin{enumerate}[(1)]
> \item foo
> \item bar
> \end{enumerate}
> ...
> --8<---------------cut here---------------start------------->8---
> 
> Inserting the \usepackage from the org file is no problem:
> 
> --8<---------------cut here---------------end--------------->8---
> #+LATEX_HEADER: \usepackage{enumerate}
> ...
> --8<---------------cut here---------------end--------------->8---
> 
> 
> Getting the argument to the enumerate environment in the right place is
> another matter. I think the only way is to redefine org-list-generic-to-latex
> like this (add this to your initialization file, .emacs or whatever, after you
> load org):
> 
> --8<---------------cut here---------------start------------->8---
> (require 'org-list)
> 
> (defun org-list-to-latex (list &optional params)
>  "Convert LIST into a LaTeX list.
> LIST is as returned by `org-list-parse-list'.  PARAMS is a property list
> with overruling parameters for `org-list-to-generic'."
>  (org-list-to-generic
>   list
>   (org-combine-plists
>    '(:splice nil :ostart "\\begin{enumerate}[(1)]\n" :oend "\\end{enumerate}"
> 	       :ustart "\\begin{itemize}\n" :uend "\\end{itemize}"
> 	       :dstart "\\begin{description}\n" :dend "\\end{description}"
> 	       :dtstart "[" :dtend "] "
> 	       :istart "\\item " :iend "\n"
> 	       :icount (let ((enum (nth depth '("i" "ii" "iii" "iv"))))
> 			 (if enum
> 			     ;; LaTeX increments counter just before
> 			     ;; using it, so set it to the desired
> 			     ;; value, minus one.
> 			     (format "\\setcounter{enum%s}{%s}\n\\item "
> 				     enum (1- counter))
> 			   "\\item "))
> 	       :csep "\n"
> 	       :cbon "\\texttt{[X]}" :cboff "\\texttt{[ ]}"
> 	       :cbtrans "$\\boxminus$")
>    params)))
> --8<---------------cut here---------------end--------------->8---
> 
> The only change is the definition of :ostart. Not a very flexible method, 
> but it will serve in a pinch. ngz et al. might have better ideas.
> 
> I should say that there are other ways to customize enumeration labels
> in LaTeX - see e.g. http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate -
> but afaict they would all require some rewiring of the above function, similar
> to the above.
> 
> Nick
> 
>> Cheers,
>> 
>> Marius
>> 
>> On 2011-10-13, at 11:37 , suvayu ali wrote:
>> 
>>> On Thu, Oct 13, 2011 at 11:11 AM, Marius Hofert
>>> <marius.hofert@math.ethz.ch> wrote:
>>>> Dear all,
>>>> 
>>>> In the manual, I found that numbered lists can be created with 1), 2), ... or 1., 2., ...
>>>> How can I get numbered lists like this: (1), (2),...?
>>>> I found org-list-demote-modify-bullet, but the help (and a google search) did not help me in finding a solution to this.
>>>> 
>>> 
>>> I don't think you can. But you can customise latex export (maybe even
>>> html export, but I don't know) to show lists like that in the exported
>>> file.
>>> 
>>> I hope this helps.
>>> 
>>>> Cheers,
>>>> 
>>>> Marius
>>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Suvayu
>>> 
>>> Open source is the future. It sets us free.
>> 
>> 
>> 

  reply	other threads:[~2011-10-13 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 19:10 Nick Dokos
2011-10-13 20:00 ` Marius Hofert [this message]
2011-10-13 20:28   ` Nick Dokos
2011-10-14 11:31     ` Nicolas Goaziou
2011-10-14 12:05       ` Jambunathan K
2011-10-14 12:24         ` suvayu ali
2011-10-14 12:37         ` Marius Hofert
2011-10-14 12:14       ` Carsten Dominik
2011-10-15 14:14         ` Eric S Fraga
2011-10-15 14:21           ` Marius Hofert
2011-10-15 15:35           ` Bernt Hansen
2011-10-15 15:56           ` Carsten Dominik
2011-10-16 15:16             ` Eric S Fraga
2011-10-13 20:02 ` Alan E. Davis
2011-10-13 20:44   ` Nick Dokos
  -- strict thread matches above, loose matches on Subject: below --
2011-10-13  9:11 Marius Hofert
2011-10-13  9:37 ` suvayu ali
2011-10-13 15:26   ` Marius Hofert
2011-10-13 18:31     ` suvayu ali

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=3414CE30-6774-4566-9391-D6929BDC4C87@math.ethz.ch \
    --to=marius.hofert@math.ethz.ch \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.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).