emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC]: Uniform indentation for lists
Date: Tue, 25 Jun 2013 23:02:02 +0200	[thread overview]
Message-ID: <87ip1152gl.fsf@Rainer.invalid> (raw)
In-Reply-To: 87hagntblh.fsf@gmail.com

Jambunathan K writes:
> When lists are "normalized", the sub-lists are introduced by varying
> amout of spaces depending on the type of the parent list.  It's 3 spaces
> if the parent is numbered and 2 spaces if the parent is bulleted.
>
> 1. One
> 2. Two
>    - Bullet One
>    - Bullet Two
>      1. One
>      2. Two
>
> Oddmuse wiki and possibly Usemod (and even other Wiki engines) do a
> linear scan of text (much like what the old org-html.el used to do) and
> emits HTML by looking at thing at point.  Having the list items
> introduced by varying amout of spaces makes the parser "more" stateful.

I don't think this is ever going to work unless you restrict either the
number of items or the types of enumeration.  But you could easily
normalize on export into those formats by indenting with a number of
tabs corresponding to the indent level.  That would look strange in a
buffer (unless you set the tab-width appropriately), but it would be
parseable more easily.  But Oddmuse is in Perl, so keeping a stack of
indents really isn't a big deal (and I don't think it'd be in other
languages like Python, PHP or Ruby).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2013-06-25 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 21:58 [RFC]: Uniform indentation for lists Jambunathan K
2013-06-25  9:44 ` Suvayu Ali
2013-06-26  4:38   ` Jambunathan K
2013-06-25 15:33 ` Carsten Dominik
2013-06-25 21:02 ` Achim Gratz [this message]
2013-06-26  4:27   ` Jambunathan K

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=87ip1152gl.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).