emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Marius Hofert <marius.hofert@math.ethz.ch>,
	Emacs help <emacs-orgmode@gnu.org>,
	nicholas.dokos@hp.com, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: How to get numbered lists (1), (2), … ?
Date: Sat, 15 Oct 2011 15:14:54 +0100	[thread overview]
Message-ID: <87hb3ae3z5.fsf@ucl.ac.uk> (raw)
In-Reply-To: <367FB6B9-C653-47C0-BBD9-02A665402353@gmail.com> (Carsten Dominik's message of "Fri, 14 Oct 2011 14:14:23 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On 14.10.2011, at 13:31, Nicolas Goaziou wrote:

[...]

> 
>>  I have nothing against (1) as item bullets, as it doesn't interfere
>>  with any existing Org syntax.
>
> That is not the only criterion.  Adding new syntax elements make more
> ASCII sequences special.  The Org markup is a heuristic set of
> special elements, and there is merrit in keeping it small.  We already
> have more bullets and in particular numbered types - and so far
> I have not seen a compelling reason to add more.
>
> - Carsten

I am in the "keep it simple school".  So long as org allows me to
distinguish between numbered and unnumbered itemised lists, I am
happy.  I actually would prefer less choices than there are currently
because I would like to get to my choice more quickly when I do use
C-c - to change the type!

To me, org is about information and time management, not about
formatting.  YMMV, of course!

To be blunt, I would be happy with "-" and "1." in org, knowing that I
can customise upon export if necessary!  I'm not suggesting we go this
far, however ;-)

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.7 (release_7.7.381.g05ea)

  reply	other threads:[~2011-10-15 14:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 19:10 How to get numbered lists (1), (2), … ? 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
2011-10-14 12:37         ` Marius Hofert
2011-10-14 12:14       ` Carsten Dominik
2011-10-15 14:14         ` Eric S Fraga [this message]
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=87hb3ae3z5.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=marius.hofert@math.ethz.ch \
    --cc=n.goaziou@gmail.com \
    --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).