Ambiguity in unordered list item definition

[Pete D.]

gemini-request at lists.orbitalfox.eu wrote:
> Message: 6
> Date: Sun, 31 May 2020 20:21:17 +1000
> From: Thomas Karpiniec<tkarpiniec at icloud.com>
> To: Gemini application layer protocol<gemini at lists.orbitalfox.eu>
> Subject: Re: Ambiguity in unordered list item definition
> Message-ID:<20200531102117.GA48485 at allanon.local>
> Content-Type: text/plain; charset=us-ascii
>
> All makes sense to me!
>
> On Sun, May 31, 2020 at 10:09:46AM +0000, solderpunk wrote:
>> Solutions that don't involve changing the spec:
>>
>> * Authors could take care to introduce a leading space before text lines
>>    which begin with emphasised words.
>> * Geminispace could adopt a convention of emphasising words like_this_
>>    instead of like*this*  (or any other way not involving *s).
> I didn't think of such a simple workaround (the leading space). You're
> right, I expect it would become common knowledge that you have to look
> out for that while composing gemini text.
>
> Not worth making breaking changes for in any case.
>
> Cheers,
>
> Tom


Doesn't it make more sense to do the *reverse* (see what I did there?), 
by requiring bullet lines to have a space *after* the *?
Because the normal standard for "ascii bold" has no spaces between the 
leading * and the bolded word, as you can see in my mail (if it hasn't 
been already rendered in bold by your mail program.

It would make sense for a bullet to be a space away from the text it is 
bulleting, so that ^[[:star:]][[:space:]] would be a bulleted list, 
while [[:star:]]Thing I want to emphasize[[:star:]]

So only really sloppy ascii-type text would break this, and so then 
maybe it should. And most bulleters would be doing this already (I see 
that that's what I did for my bullets, I'm used to mediawiki, and 
markdown is the same

https://wordpress.com/support/markdown-quick-reference/

    Bullet Lists

    * Item * Item