emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>,
	nicholas.dokos@hp.com, Marius Hofert <marius.hofert@math.ethz.ch>,
	Emacs help <emacs-orgmode@gnu.org>
Subject: Re: How to get numbered lists (1), (2), … ?
Date: Fri, 14 Oct 2011 14:24:21 +0200	[thread overview]
Message-ID: <CAMXnza1e1OinL3pc7zqmx2oLrmyW5d21YRfO+CrRVYR=rK4AJA@mail.gmail.com> (raw)
In-Reply-To: <817h47lqwc.fsf@gmail.com>

Hi everyone,

On Fri, Oct 14, 2011 at 2:05 PM, Jambunathan K <kjambunathan@gmail.com> wrote:
> Is it psychologically very taxing to see 1. instead of a (1) in an Org
> buffer. Could it be so taxing that a user's productivity will be
> impacted by it?

For my personal use I don't care much as long as there are
ordered/enumerated and unordered/plain lists to choose from, after all
only the exported file is for public consumption. :) However I
strongly feel _against_ the '*' syntax. Its too close to a headline.
It is also unusable if one chooses not to use indentation for the text
under a headline (e.g. below). I often prefer this as deeply nested
(say, level 4) headlines often start to run out of columns due to

** Heading

Some list
* list item 1
* list item 2

> Or
> Is it that more varieties of bullets is needed for creating "rich"
> deeply nested lists so that each level of the list can take on a
> different bullet for better differentiation.

This is pretty much the reason I switch list types. Something like:

1) some broad point
   + Case 1
     - comment on something of note
   + Case 2
2) another broad point

That said, I would probably use the customize option.


Open source is the future. It sets us free.

  reply	other threads:[~2011-10-14 12:24 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
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 [this message]
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:

  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='CAMXnza1e1OinL3pc7zqmx2oLrmyW5d21YRfO+CrRVYR=rK4AJA@mail.gmail.com' \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=marius.hofert@math.ethz.ch \
    --cc=n.goaziou@gmail.com \
    --cc=nicholas.dokos@hp.com \


* 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


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).