Logging/tracing possibility

[kkokosa]

It is more question than a bug report - is there possibility to trace/print somehow how the slide is being processed? I have situation that without any sense, one part of incremental slides is not displayed. And I can't have any point of entry of trying to understand what's going on there.

Just for reference, this is the slide:

---
### Generations

Advantages:

--
- collect only one generation (and younger) - less *mark*/*sweep*/*compact* work to do (which makes smaller overhead, shorter pauses)

--
- more often collect young generation (recently created objects) - it should be **productive**, most of them will die (well, "infant mortality" 😱)

--
- avoid processing the old, surviving objects again and again

--
Drawbacks:

--
- need to handle references between generations

--
- violating expected behavior may be painful

And, "Drawbacks" is not printed.

[tripu]

I don't remember about debugging/verbose options off the top of my head.

One thing you can do is check how marked (that's the Markdown library we use here) processes your input: live test. And yes, it interprets that part weirdly. If you insert an empty line between -- and Drawbacks: it looks better, but still Remark does not show that line, and the list looks broken after that part.

But I found a workaround: see this pen (the second slide).

I hope that helps!

[kkokosa]

Thanks, indeed it helps! And marked live test is also super useful.