emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Michael Strey <mstrey@strey.biz>
Cc: emacs-orgmode@gnu.org
Subject: Re: [html] non-lists showing up as lists
Date: Mon, 3 Jun 2013 12:05:47 +0200	[thread overview]
Message-ID: <A738B5A8-B866-47F8-9812-1D6EE02159C3@gmail.com> (raw)
In-Reply-To: <87mwr78qpl.fsf@strey.biz>


On 3 jun. 2013, at 11:54, Michael Strey <mstrey@strey.biz> wrote:

> Hi everyone,
> 
> Just for completeness
> 
> Carsten Dominik <carsten.dominik@gmail.com> writes:
> 
> [...]
> 
>> Possibilities:
>> 1. We could change the parser to ignore lists where the first
>>   item does not start with `1.' or `a)'.  But this would
>>   be a pretty serious change.
>> 
>> 2. We could implement a good function that could find problematic
>>   cases, so that they can be fixed by hand.  This is basically
>>   what Nick proposed - only it would be implemented in Lisp.
>> 
>> 3. We could implement a function that finds and fixes such issues.
>>   It would basically scan the buffer and find lists that have
>>   only a single item, not starting with 1, and change the wrapping
>>   to fix it.
> 
> 4. Define that lists alway have to have a newline in front of them.
> 
> 5. Define that lists always have to be indented.


Hi Michael,

I think this would break too many legacy Org files.  It would
also cause problems for sublist, so you could no longer
make compact deep lists.

But thanks for the input.

- Carsten

> 
> 
> My favourite would be 4.
> 
> 
> Michael Strey
> -- 
> mailto:mstrey@strey.biz
> http://www.strey.biz

  reply	other threads:[~2013-06-03 10:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  9:54 [html] non-lists showing up as lists Michael Strey
2013-06-03 10:05 ` Carsten Dominik [this message]
2013-06-03 16:28   ` Samuel Wales
2013-06-04 10:02     ` Bastien
2013-06-04 17:49       ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2013-06-06 10:26 Michael Strey
2013-05-31 16:54 Samuel Wales
2013-05-31 17:01 ` Nicolas Goaziou
2013-05-31 20:39   ` Alan L Tyree
2013-06-01  6:39     ` Nicolas Goaziou
2013-06-01 19:35       ` Alan L Tyree
2013-06-02  7:57         ` Nicolas Goaziou
2013-06-02  9:12           ` Nicolas Goaziou
2013-06-02 20:24           ` Alan L Tyree
2013-06-02 21:40             ` Nick Dokos
2013-06-02 23:05               ` Alan L Tyree
2013-06-03  2:17                 ` Nick Dokos
2013-06-03  4:29                   ` Alan L Tyree
2013-06-03  5:40                     ` Samuel Wales
2013-06-03  5:45                       ` Alan L Tyree
2013-06-03  7:52                         ` Carsten Dominik
2013-06-03 19:59                           ` Alan L Tyree
2013-06-06 16:37                       ` Bernt Hansen
2013-06-06 17:25                         ` Samuel Wales
2013-06-01 20:10     ` Samuel Wales
2013-06-01 20:18       ` Samuel Wales
2013-06-01 22:58         ` Alan L Tyree

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=A738B5A8-B866-47F8-9812-1D6EE02159C3@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mstrey@strey.biz \
    /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).