mirror.dongdigua.github.io/gmi
2023-06-07 20:34:10 +08:00
..
docker explain zh-en mix, ident, docker typo 2023-06-07 20:34:10 +08:00
.directory-listing-ok gmi: README, new disable_fish_completion 2023-05-03 12:07:17 +08:00
annoying_project.gmi new post: annoying project 2023-03-31 20:42:44 +08:00
cleanup_home.gmi gemini play with docker 2023-05-26 19:21:35 +08:00
collections.gmi explain zh-en mix, ident, docker typo 2023-06-07 20:34:10 +08:00
disable_fish_gpg_completion.gmi gmi: README, new disable_fish_completion 2023-05-03 12:07:17 +08:00
re.gmi multiple content file updates 2022-12-15 12:35:38 +08:00
README.gmi gmi: README, new disable_fish_completion 2023-05-03 12:07:17 +08:00
scicraft_update.gmi huge structural change: legacy_md, gmi in folder 2023-06-06 17:13:58 +08:00

# Gemtext

## Why?
* I like plaintext
* gemtext is lightweight
* no format conversion, just serve it

## Linewrap?
I usually do not use linewrap when I'm writing, because it makes me clearer
and more logical than put everything together, and I like to view text
shorter than 2/3 of the screen, and it is easier to nevigate in editor
(jump by line instead of jump by word in a long line).
When exporting org to html, I add \n:t so the export process will keep my
linebreak, so on website it is also not a mess.

But in gemini, it's recommended to write long lines[1], and such as in elpher client, it wraps line in 79 character, so I need to either write within 80 column, or write long lines and give the linewrap to "leave it up to the receiving Gemini client to wrap your lines to fit the device's screen size and the user's preference"

I will wrap line freely as I want, neither 80 column rule[2] nor long line.


=> gemini://gemini.circumlunar.space/docs/gemtext.gmi [1]: Gemini Doc
=> https://www.emacswiki.org/emacs/EightyColumnRule   [2]: EmacsWiki EightyColumnRule