Back in the pre-GUI era, I did this with all my posts and comments online. All fully-justified, both margins, without any extra whitespace: just careful choice of words, and occasional (but always normal standard) abbreviations.

It was fun, once practised it barely slowed me down, and when people noticed it blew their minds.

Then along came GUIs and proportional fonts and made it all invisible. :'(

Michael Hart, founder of Project Gutenberg, was known for this style.

https://en.wikipedia.org/wiki/Michael_S._Hart#Writing_style

See examples at http://hart.pglaf.org/ .

Huh! I never knew. Never saw an intentional example on the wider internet before. It was a Thing™ for me and about 2 others on the old UK CIX service.

I have found my people.

Amazing, thank you for this.

I thought I was alone!! wipes tears of joy

Well. Lorem Ipsum vs Donald Knuth. I think they both suck. I have a different hero. Linus Torvalds. He IS good AND actually delivers.

I enjoyed the video. However, both the author and Donald Keith strike as two people who are mainly motivated by aesthetics (which is supremely ironic as they almost define themselves as being the opposite of Loren Ipsum). I like people who deliver results.

I think the author mostly likes the appearance of someone who pays attention to detail. He says that in a movie if it's obvious that the coffee cups are empty, he notices and bothers him. 3 minutes later in his video he has a guy using his laptop at the beach where glare would make it impossible to see anything on the screen.

We'll give "real actual bug" a pass :)

There is a complete super metroid walkthrough using this technique : https://gamefaqs.gamespot.com/snes/588741-super-metroid/faqs...

cfg.linebreaks: LLM-plain-tex

/s

It's a bit easier to do when you don't limit yourself to exactly 80-char per line

  Those commits were 
  72-chars per line.
  Which is easier to
  do than EXACTLY 80
  character per line

72 characters per line is a common standard for git commit messages. If you use vim, the syntax highlighting will nudge you to exactly that number.

https://tbaggery.com/2008/04/19/a-note-about-git-commit-mess...

72 characters is the standard limit for Git though. This convention has a long tradition from the text-mode days of email and Usenet in 80-column terminals/screens, where 72 characters allowed for the addition of a reasonable number of quoting levels (indicated by prefixing quoted lines with “>”), and/or for other line markers, before exceeding the screen width and having to reformat.

COBOL code seems to live in 72 columns, with the last 8 columns of a punch card were 'free for programmer use'.

Now I am wondering if somehow, some ancient COBOL limit ended up in git because every tool picked it up as convention from an older tool.