emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Bugs and suggestions for Org 4.70
Date: Fri, 13 Apr 2007 15:11:22 +0200	[thread overview]
Message-ID: <87odlsto5h.fsf@bzg.ath.cx> (raw)
In-Reply-To: <efb0f4fe30c8efaed1d13239ce276594@science.uva.nl> (Carsten Dominik's message of "Fri\, 13 Apr 2007 14\:38\:35 +0200")

Carsten Dominik <dominik@science.uva.nl> writes:

>> Mmhh. It may require a full rewriting of the lists parsing funcs; i
>> didn't check your code for that, but having spent a good amount of time
>> trying to implement something like this for my old bhl-mode, I know list
>> parsing is always challenging.
>
> Well, in this case it is even impossible.  How could
> you distinguish the two?  I guess the only way would be to require an empty
> line before a new list item, but that is not acceptable.

The approach i tried to implement was to delimit list environments before
matching list items.  

For example "[\t ]*\([0-9]+\|[-+o]\) " would match a list item and this
item will start a new list environment.  Depending on (match-string 1),
this list environment would be ordered, unordered, etc.  

Then the parser would try to find the end of the list environment before
doing any conversion.  The end of a list environment is often a new line
starting with something else than tabs/whitespaces (this definition my not
be sufficient, of course).

Finally, within the list environment (a region), the parser would process
each list item of a certain type, ignoring number in unordered lists and
dashes in ordered lists ...  but enough with speculations, i just wanted 
to sketch the idea.

> Yes, interesting idea, implementation not very fast I am afraid, too many
> other things on my plate right now.

Thanks very much -- i think everyone agrees it's already difficult to
follow the amazing pace of Org development !

-- 
Bastien

next prev parent reply	other threads:[~2007-04-13 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 20:10 Bugs and suggestions for Org 4.70 Bastien
2007-04-13  8:41 ` Carsten Dominik
2007-04-13 10:41   ` Giovanni Ridolfi
2007-04-13 12:10   ` Bastien
2007-04-13 12:38     ` Carsten Dominik
2007-04-13 13:11       ` Bastien [this message]
2007-04-18  6:55     ` Carsten Dominik
2007-04-18  9:17       ` Bastien

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=87odlsto5h.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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

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