mirror of
				https://github.com/go-gitea/gitea.git
				synced 2025-10-29 10:57:44 +09:00 
			
		
		
		
	GH has different HardBreaks behaviour for markdown comments and documents. Comments have hard breaks and documents have soft breaks - therefore Gitea's rendering will always be different from GH's if we only provide one setting. Here we split the setting in to two - one for documents and one for comments and other things. Signed-off-by: Andrew Thornton art27@cantab.net Changes to index.js as per @silverwind Co-authored-by: silverwind <me@silverwind.io> Changes to docs as per @guillep2k Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
This commit is contained in:
		| @@ -152,7 +152,10 @@ Values containing `#` or `;` must be quoted using `` ` `` or `"""`. | ||||
|  | ||||
| ## Markdown (`markdown`) | ||||
|  | ||||
| - `ENABLE_HARD_LINE_BREAK`: **true**: Render soft line breaks as hard line breaks, which | ||||
| - `ENABLE_HARD_LINE_BREAK_IN_COMMENTS`: **true**: Render soft line breaks as hard line breaks in comments, which | ||||
|   means a single newline character between paragraphs will cause a line break and adding | ||||
|   trailing whitespace to paragraphs is not necessary to force a line break. | ||||
| - `ENABLE_HARD_LINE_BREAK_IN_DOCUMENTS`: **false**: Render soft line breaks as hard line breaks in documents, which | ||||
|   means a single newline character between paragraphs will cause a line break and adding | ||||
|   trailing whitespace to paragraphs is not necessary to force a line break. | ||||
| - `CUSTOM_URL_SCHEMES`: Use a comma separated list (ftp,git,svn) to indicate additional | ||||
|   | ||||
		Reference in New Issue
	
	Block a user