💾 Archived View for rawtext.club › ~sloum › geminilist › 002859.gmi captured on 2020-11-07 at 03:11:35. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2020-10-31)

-=-=-=-=-=-=-

<-- back to the mailing list

Bug reports: Multiple spaces in links; Cmd+S unreliable (was: Re: [ANN] Lagrange - A Beautiful Gemini Client)

skyjake skyjake at dengine.net

Mon Oct 12 07:14:23 BST 2020

- - - - - - - - - - - - - - - - - - - 

On 12. Oct 2020, at 3:38, Nathan Galt <mailinglists at ngalt.com> wrote:

Eh. I wouldn’t wish that on a client author. That user listing already looks kind of bad in amfora(1) already with my fairly-narrow text-width settings. I don’t think there’s a good solution here for properly-aligned text (all the preexisting proposals have been shot down or deferred or something), so my hunch is that the best option is to do nothing special.
Situations like these are why I prefaced this whole thing with “I don’t know if it’s wrong, but…”.

I recognize that in gemtext one cannot use spaces like this for alignment, while also permitting variable-width fonts and whitespace normalization. Nevertheless, I was curious about the idea of normalizing multiple spaces differently. A simple rule of 8+ spaces becoming a tab character produced nice results:

=

http://media.skyjake.fi/normalized_to_tabs.png

It was also quite simple to implement (of course, Lagrange uses a custom text renderer so stuff like this is possible without extra effort):

=

https://git.skyjake.fi/skyjake/lagrange/commit/4a3cda29bbf2494061fb1090698cf1230e43a280

I'm not advocating for this to be standard practice in clients, but I'll keep it at least for the time being in Lagrange and see if it produces adverse effects elsewhere.

--jaakko