Fossil

Check-in [1b2d6c30]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Expanded on the rules for literal/verbatim/fenced text in the /md_rules document.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 1b2d6c30ba1ab06b64e9d88186895389c2129119b00ee8d887bbff5b6d3e9d9b
User & Date: wyoung 2019-06-16 19:03:18
Context
2019-06-16
19:22
Removed the "or --allow-fork" advice output from "fossil checkin" when forcing the checkin would fork the branch. It's good for Fossil to have this option, especially for automated tooling that needs to just bull forward blindly, but it's bad advice to give to interactive users. Let them discover it via --help, if they learn of it at all. check-in: 66d55e9b user: wyoung tags: trunk
19:03
Expanded on the rules for literal/verbatim/fenced text in the /md_rules document. check-in: 1b2d6c30 user: wyoung tags: trunk
17:58
Adding a simulation (www/collisions.ipynb) for checkin collisions over a working day, given parameters like number of checkins per day. This is in support of discussion on the forum centering on this post: https://fossil-scm.org/forum/forumpost/7349f4b6e1 check-in: 950e54ef user: wyoung tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to src/markdown.md.

74
75
76
77
78
79
80
81
82























83
84
85
86
87
88
89
> Begin each line of a paragraph with **>** to block quote that paragraph.

> >
    > This paragraph is indented
> >
    > > Double-indented paragraph

> Begin each line with at least four spaces or one tab to produce a verbatim
> code block.
























## Tables ##

>
    | Header 1     | Header 2    | Header 3      |
    ----------------------------------------------
    | Row 1 Col 1  | Row 1 Col 2 | Row 1 Col 3   |







|
<
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>







74
75
76
77
78
79
80
81

82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
> Begin each line of a paragraph with **>** to block quote that paragraph.

> >
    > This paragraph is indented
> >
    > > Double-indented paragraph

## Literal/Verbatim Text ##


> There are several ways to write text in Markdown that should be
> rendered without any special interpretation.

> For inline text, you can either use \``backticks`\` or the HTML
> `<code>` tag.
>
> For blocks of text, there are several methods:
>
> 1. Indent the text using a tab character or at least four spaces.
> 2. Precede the block with an HTML `<pre>` tag and follow it with `</pre>`.
> 3. Surround the block in triple backticks (\`\`\`) either at the
> left margin or indented no more than three spaces.

> Note that unlike in [GitHub-Flavored Markdown][gfm], Fossil does not
> currently support any “info string” in [fenced code blocks][gfmf]
> after the opening sequence, including language tags

> With the standard skins, verbatim text is rendered in a fixed-width font,
> but that is purely a presentation matter, controlled by the skin’s CSS.

[gfm]:  https://github.github.com/gfm/
[gfmf]: https://github.github.com/gfm/#fenced-code-blocks

## Tables ##

>
    | Header 1     | Header 2    | Header 3      |
    ----------------------------------------------
    | Row 1 Col 1  | Row 1 Col 2 | Row 1 Col 3   |