[pmwiki-users] numbered list questions

[Patrick R. Michaud]

On Tue, Mar 15, 2005 at 10:03:20AM -0500, David Spitzley wrote:
> Why not allow "capping" of list entries with a closing # symbol? 
> 
> #First entry in the list#
> #Second entry in the list, which is
> very, very, very, very, very, very,
> very, very, very long#
> 
> Obviously, you'll need to leave the "capping" # optional for backward
> compatibility, but I think defaulting to the current block-handling
> behavior in the absence of capping would be reasonably straightforward
> ("ok, I've got a new line starting with a #, and the next # I see also
> starts a line, so I'll use the old blocking rules up through that point"
> vs "ok, I've got a new line starting with a #, and the next # I see is
> not at the start of a new line, so I'll treat everything in-between as a
> block").  I suppose nested lists could complicate things somewhat,
> though.

Yes, and it's not at all an obvious markup, and it requires a fair 
amount of "lookahead" on the part of PmWiki to see if there are any
later lines that have the capping #.  PmWiki currently works by processing
"the current line" without looking ahead to see what may be coming
(I'm not likely to change this model).

And what do we do with:

    # First entry in the list
    # Second entry in the list
    with more text
    and still more text.

    And a paragraph.  Lorem ipsum dolor sit amet, consectetuer 
    adipiscing elit. Donec metus magna, lobortis nec, auctor sit amet.

    * Here's a bullet list thrown in for fun.

    And this line has a "capping" #

*Now* what do we do?  ;-)  Is the bullet list considered part of the 
second item in the numbered list?

And the presence of capping #'s later in the text just a "spooky action
at a distance" sort of feeling to them -- i.e., it's not at all obvious
to someone looking at the "Lorem ipsum" paragraph above that it's
part of the numbered list.

Pm

> >>> "Patrick R. Michaud" <pmichaud at pobox.com> 03/15/05 9:58 AM >>>
> On Tue, Mar 15, 2005 at 12:20:26AM -0800, Carl Boe wrote:
> > 
> > I think it would be beneficial to have a some way to block-ify text 
> > blocks in such situation, and protect the block from the <li> element
> 
> > ending prematurely.  
> > [...]
> > It is not too hard to imagine ordered and unordered lists which are 
> > quite lengthy and contain several paragraphs, tables, displayed 
> > equations, etc., 
> 
> I agree with the above; however, we haven't found a list markup
> that accomplishes this and is universal enough to support other
> views of how it should work (and I haven't wanted to impose a
> particular
> view on others).  The prime candidate at the moment is to allow
> authors
> to use leading spaces to indicate that text should be part of a 
> preceding list item or block-level element:
> 
>         # list level 1, item 1
>         # list level 1, item 2.  Lorem ipsum dolor sit amet, 
>           consectetuer adipiscing elit. Donec metus magna, 
>           lobortis nec, auctor sit amet, feugiat id, augue. 
> 
>           This text is still part of list level 1, item 2,
>           because its lines are indented with spaces to the
>           same column as the above.
> 
>         # list level 1, item 3
> 
> This could cause some confusion with preformatted text.  Even so,
> I'm working on finding a way to integrate this as an extension, if
> not part of the core.
> 
> Pm
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com 
> http://pmichaud.com/mailman/listinfo/pmwiki-users