You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2022. It is now read-only.
When writing markdown files it good to insert a line break into the source file after any major punctuation (".", ";", ":"). This makes diffing the source text much easier, because if you have entire paragraphs on a single line you need to read the whole paragraph for differences.
GitBook is also making the history harder to read for a file and ultimately figureout who made the change.
Possibly we should have a branch for the raw sources and a seperate branch that has gitbook normalized files.
This behavior can also lead to suprisingly rendered files such as:
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See 6adf42c for an example.
When writing markdown files it good to insert a line break into the source file after any major punctuation (".", ";", ":"). This makes diffing the source text much easier, because if you have entire paragraphs on a single line you need to read the whole paragraph for differences.
GitBook is also making the history harder to read for a file and ultimately figureout who made the change.
Possibly we should have a branch for the raw sources and a seperate branch that has gitbook normalized files.
This behavior can also lead to suprisingly rendered files such as:
The text was updated successfully, but these errors were encountered: