Tim Huegerich

Update: I think the issue is due to missing kernel functionality in 'nbstata' that should be straightforward to implement. I hope to release it by the end of the month....

The plan is to pass any inline expressions to [sfi.SFIToolkit.macroExpand](https://www.stata.com/python/api18/SFIToolkit.html#sfi.SFIToolkit.macroExpand), making use of the '= exp' local expansion operator. So, given the following line in a .qmd file, assuming that...

> May I suggest to also allow for display and globals? And perhaps mata ‘Stata mata x’ Allowing to show the content of x? Globals should already be covered by...

On second thought, maybe we should try to match [MarkStat's features](https://grodri.github.io/markstat/documentation) for inline code: > You can quote results by including inline code as part of your narrative, using the...

Decided to keep it simple for now and just support the Stata display syntax (with no special mata support).

Good news: we're able to directly use Stata's `display` (so that you "can use all the features of display that make sense," as [Stata's docs](https://www.stata.com/help.cgi?macro#remarks8) put it) like this: https://github.com/hugetim/nbstata/blob/12fc23f00fcb14df59d6d12ea910ea45259a8ecb/nbstata/stata_more.py#L181...

To my mind, it is appropriate to have behavior tied to file format. Interactive inline output is the essence of a notebook, whereas .qmd files are mere code, akin to...

I was experiencing a similar issue (and likewise with 1.3.1). Reverting to 1.2.1 fixed it.

You can see my use case here: https://github.com/hugetim/nbstata/blob/d4ca8ab25ba4b4689434371203337cc0cb644d36/nbstata/browse.py#L206-L256