In my last post on this list I called escape codes spaghetti without much of an explaination. Tl;dr: -Do we want color in text/gemini? -If yes how should it be standardized? I really like that there are creative people out there looking for ways to push systems like gemini outside of what they are supposed to be able to do. And I don't want to decide (at least not now) if the escape code thingy is a "bug" or a feataure in most clients. The first question we have ask here is if we want color support at all: I know, that gemini should remain simple and support for colors takes away a good part of this simplicity. But there are a lot of usecases for color support. (Code highlighting, pretty ascii art, footnotes, ...) For me these are two pretty strong arguments against each other. So in case we want color support: Assuming the escape code thingy is a feataure: We should standardize which escape codes are allowed and how clients should handle them. Assuming it is a "bug": Some people (me included after thinking about it) like to see color being used in gemini so we have to find another way to put colors in while the text/gemini format should remain easy to parse and human readable. (Correct me if I'm wrong but that is how I interpret the text/gemini format: Markup that is easy to parse but still human readable if you open it in something like a text editor) If I had to standardize it I'd use custom escape sequences, similar to those already in use but optimized to be no longer than necessary that ALWAYS end in a ';'. This is not really text editor friendly, but avoids having to escape the escape caracter (I'm looking at you XML), makes it easy to parse/strip the escape sequences and if you don't you at least get very short spaghetti. In any case I'm for filtering out unwanted escape codes. I'm looking forward to get some other opinions on this. Greetings - Baschdel -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20191211/8507 60df/attachment.htm>
---
Next in thread (2 of 8): 🗣️ Sean Conner (sean (a) conman.org)