[SPECS text/gemini] Heading lines proposal

cage cage-dev at twistfold.it
Sun Jun 14 14:59:56 BST 2020


On Sun, Jun 14, 2020 at 10:16:20AM +0000, solderpunk wrote:

Hi solderpunk!

> On Sun, Jun 14, 2020 at 11:07:31AM +0200, cage wrote:

> > For example if i starts a line mentioning an IRC channel like that:
> >
> > #channel [...]
> >
> > this would be presented  to the user as an header of  level 1 which is
> > not.
> >
> > The same would be true if i mention a tag for a social network.
>
> I guess this is just as good an argument as the *emphasised* words
> clashing with list items thing.  AFAIK it hasn't been spotted in the
> wild yet, but that's probably just a function of Geminispace being young
> and small.

yes, and probably even less likely to occurs than the emphasis.

> > As for the  list item i think would  be a good idea to add  a space to
> > the header mark: so from "#" to  "#<space>" and so on for header level
> > 2 and 3.
>
> This would be covered by Petite Abeille's proposal to just put a
> mandatory space after *all* the special line indicators.
>
> Is it silly that I'm sad this would require (on account of
> ### sub-sub-headings) changing "It is possible to unambiguously
> determine a line's type purely by inspecting its first three characters"
> to "first four characters"?  It is silly.  But three just feels like a
> much more *natural* choice of entirely arbitrary small number...

:) Well i think i can sort of understand, if i would need to choose to
change  the  sentence  above  to  "It  is  possible  to  unambiguously
determine  a  line's  type  purely  by  inspecting  its  first  *four*
characters", and  remove the  sentence for  inexplicable (even  to me)
reason i would choose the second! ;-D

Anyway, i am starting writing a parser, it is refreshing (for my mind)
the fact that the syntax is so simple and still effective! :)

Bye!
C.


More information about the Gemini mailing list