💾 Archived View for rawtext.club › ~sloum › geminilist › 002327.gmi captured on 2020-11-07 at 02:49:56. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Gary Johnson lambdatronic at disroot.org
Fri Jul 24 16:25:09 BST 2020
- - - - - - - - - - - - - - - - - - -
I also support the "spaces after all line type markers" idea, And Iagree with the other poster (Paper?) that one of gemtext's bestqualities is that it is intrinsically (and intuitively) human-readableeven without rendering. It is, in fact, a totally WYSIWYG format.
Into the future! Gary
P.S. Astrobotany is going to need to update its links though...
Ryan Knipe <sario528 at gmail.com> writes:
I'm on board. It improves human readability, and ensures consistency.
On Thu, Jul 23, 2020, 2:38 PM Solderpunk <solderpunk at posteo.net> wrote:
Okay, I am happy with this idea (in fact, for a minute or two I was
thinking "didn't we already do this?!" - no, that was with list items,
to avoid ambiguity with *this* kind of emphasis).
At this point it seems like we may as well go "whole hog" and insist on
at least one space after *all* the line type markers - that would mean
quote lines starting with "
" and link lines starting with "=
". Does
anybody object to *that*? I strongly suspect that almost everybody is
actually writing their content that way anyway, but perhaps not...
Cheers,
Solderpunk
-- GPG Key ID: 7BC158EDUse `gpg --search-keys lambdatronic' to find meProtect yourself from surveillance: https://emailselfdefense.fsf.org=======================================================================() ascii ribbon campaign - against html e-mail/\ www.asciiribbon.org - against proprietary attachments
Please avoid sending me MS-Office attachments.See http://www.gnu.org/philosophy/no-word-attachments.html