💾 Archived View for rawtext.club › ~sloum › geminilist › 000344.gmi captured on 2020-11-07 at 01:25:34. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
lel lel at envs.net
Fri Jan 17 13:58:04 GMT 2020
- - - - - - - - - - - - - - - - - - - ``` On Fri, Jan 17, 2020 at 01:33:12PM +0000, solderpunk wrote: > It's possible even that what I'm about to describe is exactly what the > "long line" folks have been talking about all along without my > realising it. > ... > There is another option that I hadn't thought about until now, which > is to do only the first half of 2. above. That is, lines longer than > the viewport get broken up nicely at word boundaries into lines of > length equal to or less than the viewport width - but that's it. > Consecutive shorter lines are *not* joined together. Blank lines in > the "source" are rendered, one by one, into empty vertical space. > The renderer has no explicit concept of a paragraph. Yes, this is exactly what I was trying to say. There's no need to joinsubsequent lines together. That's just reflowing, as far as I can tell.But you don't need to reflow in that specific way unless your contentis inconveniently hard-wrapped when you want it to be resizable. Thissort of reflowing leads to loss of information if the singleline-breaks were intended and meaningful, so it makes more sense to meto not add those line-breaks into the content, but into their renderingon the client-side. This is the happiest I've been to see an email in a while honestly lol ~ lel