Rob Norris

`tut:silent` doesn't work because of the trailing space.

simplified inline hack

1

One way to satisfy requests for inlining code (as discussed [here](https://gitter.im/tpolecat/tut?at=57058dd9799f8c895eb51619)) would be to turn `````` The secret is ```tut:inline println("igloo") ``` and this is the rest of the sentence....

Suggested by retronym ... worth a go - [this](https://github.com/scala/scala/blob/2.11.x/test/junit/scala/tools/nsc/interpreter/CompletionTest.scala) - and [this](https://github.com/scala/scala/blob/2.11.x/src/repl/scala/tools/nsc/interpreter/PresentationCompilerCompleter.scala) - and [this](https://github.com/scala/scala/blob/2.11.x/src/repl/scala/tools/nsc/interpreter/PresentationCompilation.scala)

From the Gitter channel: > @fthomas are there plans to check function / type names outside of tut sheds? I just stumbled about a doc where I've renamed a function...

`StateT` and `IO` probably need to be trampolined.

They don't work because compiler errors are worded differently; need specific `expect` files for each scala version we're testing.

reuse repl instance instead of creating a new one for each page

1

Could be tricky since it wants a constant writer.

consider a different approach for displaying error messages

3

Inline error messages split the code up, which is disorienting, hard to read and very hard to edit. Their location seems approximate (sometimes the error is above, sometimes below) and...

The recent fix for #70 helps (thanks!) but there is still a problem with the machinery that attempts to guess which highlighter to use. Can we not support GFM style...

``` [info] ! Combinator.choice/1: Falsified after 90 passed tests. [info] > ARG_0: "枇噻㷻讃" [info] > ARG_1: "" [info] > ARG_2: "\u0000" [info] > ARG_2_ORIGINAL: "얐꽭ḋ廧뀎陏ၢ茁迏ἵ䝨쑥醹黜㱩隢ଧꜾ㹉᥂乬䙗⫑뼂ữ॥鈘䇏蠵ܺ漽탳蜥礵㓹䉔눎只睃绪㚱뽈ి蹈쌁쳪鶙ꝺ愛ꄒ늾ᶰ榉泆⑦캳蔅௯抡⦡喝ᥡ讔ᅄ벎ꎏ誹ᑁ涝寣㒿ɜ烞ə윕" ```