I somewhat agree with lel at envs.net depending on how you think of raw mode. If indeed the thought is that raw is truly 100% raw and cannot even make links, then I agree. However, the current state of every gemini client I have used is that of a hybrid raw mode in which there is no text reflow (I have not seen a client implement reflowed text, only wrapped text) and text is rendered as written, with the one single exception of lines beginning with `=>`. This is lightweight and is working now. It is coded and people are using it. It is what we have: a raw mode (potentially wrapped), with the ability to add links. So, given the above, the desire is to _also_ have reflowed content. As such I think adding in tags to start and end reflow makes sense, rather than pretend that what we have and are doing is reflowed text and that we are adding raw text mode... which just isn't the case for any extant client that I have encountered. The ability to add line breaks within reflowed text has also not been discussed and seems to me to complicate markup. Unless we are adopting the double line break thing that some markup languages use... but I have found that to be annoying to work with (it leaves unclear what happens with triple newline for example and also leaves room for weirdness in files that use \r\n line endings).
---
Previous in thread (8 of 9): 🗣️ lel (a) envs.net (lel (a) envs.net)