
More precisely, do this for nested flows with the "refcontent" style. For instance this Scribble: @margin-note{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.} Will render as this Markdown: > 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. A site like GitHub.com will render this in a block-quote style suitable for notes: > 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. original commit: a3800cdc94d5f0c1b361d6e3ead6c1ebceb66288
1.5 KiB
1.5 KiB
```scheme
(require racket/string)
* Item 1.
* Item 2.
## 1. Section
[I am a hyperlink to Racket.](http://www.racket-lang.org/)
_Italic_. \_Just underlines\_.
**Bold**. \*Just asterisks.\*
“Dobule quoted”. ‘Single quoted’.
`Hi, world.`
`A “quote”.`
`Second line.`
`Last line.`
The end.
`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.`
```scheme
(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.