c7f0f37159
Had been specifying Scheme lexer for code blocks, while waiting for new Racket lexer to wend its way from Pygments to Pygments.rb to Linguist to GitHub. That day is almost here: Linguist will soon update and deploy to GitHub. And Racket 5.3.2 is about to release. As a result, I think this is the correct time to switch to the Racket lexer: It should be live on GitHub by the time people are using Racket 5.3.2. /cc @rmculpepper -- I think this commit should go into the 5.3.2 release. original commit: 4d3a5bad04d0958c71c70aaed0ab2c2055c5f272
1.8 KiB
1. Section
This is a top-level section.
1.1. Subsection
This is a subsection.
1.1.1. Subsubsection
This is a subsubsection.
Here is an itemize:
-
Item 1.
-
Item 2.
Here is a hyperlink:
Italic. _Just underlines_.
Bold. *Just asterisks.*
“Dobule quoted”. ‘Single quoted’.
Example of vebatim:
Hi, world.
A “quote”.
Second line.
Last line.
Another example of verbatim, with ticks/quotes:
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Example of a defmodule:
(require racket/string)
Example of a defproc:
(make-string k [char]) -> string?
k : exact-nonnegative-integer?
char : char? = #\nul
Returns a new mutable string of length k where each position in the
string is initialized with the character char
Note: This is a note. Let’s make it long enough that the markdown output will have to line-wrap, to make sure the > mark starts each line properly.