💾 Archived View for bbs.geminispace.org › u › freezr › 2441 captured on 2023-11-14 at 09:34:14. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Re: "✍ Gemtext enhancements..."
@stack there you go…
— omg.pebcak.club/~freezr/gemlog/2023-06-26-four-years-of-gemini-and-so-what.gmi
Jun 26 · 5 months ago
@freezr I like your ideas, although chances are no one will bother at this stage. There are so many ways to make a better Gemini... For instance I wish gemtext parser could just look at the first character of a line and do something - right now it is one, two, or three characters, sometimes with a space after, sometimes modal, etc. Early on I could not believe that a protocol with a handful of possible line types marks each one using a different strategy! It is purely sadistic. But whatever.
@stack I continue pushing even though what I do best it is just farting loud... 🤣
As a wise man said, smile and everyone will smile with you; fart -- and you'll be smiling alone.
@stack thanks… 🙏
I don't think this is a good idea. It handles pretty basic use cases poorly, and advanced ones not at all. I suggest burning tables directly into the gemtext.
— gemi.dev/gemlog/2023-06-30-tables-in-gemtext.gmi
As for ordered lists. I just use this:
It works with all clients, avoids needing syntax to define using numbers vs letters vs whatever. avoids syntax for (re)starting an ordered list at a number besides 1. In a lot of ways this is like "burning" a table into gemtext. You are burning the order into the list
Clients can be smart and detect this pattern if they want, and display it as an ordered list, just like some clients like Lagrange detect emojis as the first character of a link and render that in a special way.
✍ Gemtext enhancements... — I believe I found a method to make tables and ordered list in GemText without any major changes. I will post my take on this subject ASAP! 🤫