Re: Use {@x} to End a Numbered Example List, where x is identifier for this specific list

[John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>]

No, you can't have two separate example lists in a document.
If you use (@foo1) and (@foo2) in example lists, it simply
gives you a way to refer back to these list items later,
e.g. "see item (@foo2)."

LaTeX has a sophisticated mechanism of counters which allow
you to have multiple automatically numbered lists, with
different numbering styles etc.  Pandoc's markdown is much
simpler, and I'm not convinced that we should try to
do everything you can do in more complex formats.

Hossam Ghorab <hossamghorab404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Sorry for the bad wording. I really admire your work and didn't mean to 
> underestimate your kind efforts.
>
> I'm aware of the  numbered example list 
> <https://pandoc.org/MANUAL.html#numbered-example-lists>, the thing is if I 
> want to use 2 lists, I intuitively give them different identifiers e.g 
> '(@foo1)' and '(@foo2)'. However, they are parsed as a single list. I still 
> can't make make multiple different lists, it's a single list throughout the 
> document.  Please enumerate us, is it possible to have more than a single 
> list of this type in a single document? If yes, is the suggested syntax 
> applicable?
>
>
>
> On Wednesday, December 29, 2021 at 9:36:18 PM UTC+2 John MacFarlane wrote:
>
>> Hossam Ghorab <hossamg...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > Thanks for sharing your idea. Maybe we can post our suggestions 
>> somewhere 
>> > where core Pandoc developers can see? They don't seem very active here.
>>
>> Really? I've posted here 320 times in the last year.
>>
>> Note that the syntax `(@foo)` is already used for regular example
>> lists; `foo` identifies the specific list number, not a list
>> series.
>>
>>
>> >> This has come up before, and it wouldn't surprise me if there is 
>> already 
>> >> an issue for it, although I can't find one at the moment. (For all that 
>> I 
>> >> know I might even have opened such an issue myself but don't remember 
>> it.) 
>> >> I have a file with a proposal, but I don't remember if I ever posted 
>> it. My 
>> >> idea was to use curly brackets to distinguish counters from citations 
>> so 
>> >> `(@{foo})` would be the counter named `foo` and then optionally a colon 
>> and 
>> >> a number/letter which gives the numbering type and the start number as 
>> for 
>> >> regular lists so `@{foo:10}` = the counter `foo` starting at 10 with 
>> >> decimal numbers, `@{bar:x}` = the counter `bar` starting at 10 with 
>> >> lowercase roman numbers, `@{baz:J}` = the counter `baz` starting at 10 
>> with 
>> >> upper alpha numbers, with the `:N` bit being ignored except at the 
>> first 
>> >> occurrence of the counter, or maybe resetting the counter, as I imagine 
>> >> that one of the main usea of this feature might be to have a separate 
>> count 
>> >> for each chapter, and then resetting the same counter makes sense.
>> >>
>> >> Den ons 22 dec. 2021 21:17Hossam Ghorab <hossamg...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>> >>
>> >>> Dear all,
>> >>>
>> >>> Regarding the [continued numbered example lists](
>> >>> https://pandoc.org/MANUAL.html#numbered-example-lists). A problem is 
>> >>> that we can only define a single list that gets continued along the 
>> >>> document. Why don't we use `(@x)` where we can simply call the 
>> identifier 
>> >>> of this list, x, whenever we want to continue it's numbering? The list 
>> >>> identifier may be any character not just a number. Something like:
>> >>>
>> >>> ``` (@1) element 1 of list 1 (@1) element 2 of list 1 
>> >>> --interruption---- List 2: (@2) element 1 of list 2 (@2) element 2 of 
>> >>> list 2 ---- interruption---- List 1 continuous: (@1) element 3 of list 
>> 1
>> >>> (@1) element 4 of list 1
>> >>> ```
>> >>> This is a primary suggestion open to all kinds of arguments. And many 
>> >>> thanks to [@cderv](https://github.com/cderv) who has been a great 
>> help 
>> >>> regarding Pandoc issues facing Rmarkdown users. 
>> >>>
>> >>> -- 
>> >>> You received this message because you are subscribed to the Google 
>> Groups 
>> >>> "pandoc-discuss" group.
>> >>> To unsubscribe from this group and stop receiving emails from it, send 
>> an 
>> >>> email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> >>> To view this discussion on the web visit 
>> >>> 
>> https://groups.google.com/d/msgid/pandoc-discuss/bae691bb-767f-4d26-9e6e-21886fea9bd2n%40googlegroups.com 
>> >>> <
>> https://groups.google.com/d/msgid/pandoc-discuss/bae691bb-767f-4d26-9e6e-21886fea9bd2n%40googlegroups.com?utm_medium=email&utm_source=footer
>> >
>> >>> .
>> >>>
>> >>
>> >
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups "pandoc-discuss" group.
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/febfa13f-00aa-4526-875e-5e33c024d02dn%40googlegroups.com
>> .
>>
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f60b6c88-99e5-4d3f-881d-63c5063f47d5n%40googlegroups.com.