Steve Purves

Thanks @chrisjsewell for this issue and all the information/options added in one place! > Note: most of the following comments is in the context of thebe/live code I think that...

Should we consider transparency of the process of exposing variables over being kernel agnostic? This thought comes from a conversation with someone who is an RMarkdown user, and specifically: >...

@chrisjsewell what I meant is that no markup or additional code required in order to expose an output. (The glue'ing []or whatever equivalent process is not visible to the user)...

@chrisjsewell it seem that this would mean executing code on demand when a markdown cell containing a variable is encountered? wouldn't that lead to unexpected results? i.e. computation is designed...

@fwkoch just one question for now - on the > "This feels bad to me, there are now export cases where toc[0] just gets popped off and ignored..." does this...

@agoose77 re: >> Nested TOCs - this feature helps keep constantly changing projects organized - one folder may be allowed to autogenerate the toc from contents while another folder is...

interesting package in this comment https://github.com/executablebooks/jupyter-book/issues/815 and the issue mentioned above

@HelgeGehring thanks for the question - we're refining how thebe integrates with the base myst-theme packages and components - where there is some flakiness and edge case failures still to...

The hesitance here is that the state management of notebook execution in `myst-theme` is essentially entwined with the react render state. There are already some undesirable effects and edge cases...

The effects are intermittent and race condition like, so definitely annoying. I hit them when trying to execute a notebook "quickly" after the session has started, so hit the power...