When I want a function that returns a raw string that is not interpreted as CommonMark, I use HTML return mode. Example:
```space-lua
function rawExample()
return { html = '1. foo' }
end
```
If I do not use the HTML return mode, the result is interpreted and displayed as numbered list item, which is expected (if invoked as first thing on a line).
I ask about the status of the return table key/method html in the future. I think we should have real raw return mode too: return { raw = '1. foo' } that will guarantee that it won’t get interpreted in any way in the future. I can imagine the HTML return mode can gain some special meaning in the future and therefor it’s “rawness” can not be guaranteed in the future.
The raw return mode will just put what’s in it in the place of the call, and nothing else. It’s therefor very close to the HTML return mode, of course, but without additional semantic. Also, there is no need to distinquish between inline and block, because these can be easily distrinquished by series of EOLs in the raw output.