It's a known limitation, yes. We currently have no way to express that
we expect inline content ''only'' from a macro. So I think that we need
to expand the API a bit, for example by adding an `is_inline` method on
the macro providers. That way we could only expand the macros which give
us the guarantee to produce inline content.
Ok, so here's a patch that implements this. It also illustrates how a
macro can sometimes produce inline content, sometimes not (here the
TicketQueryMacro, producing inline content for the count and compact
format). In addition, if a macro wants to adapt its generated content to
the current expected output, it could look at the type of the formatter.
But in general it should be the other way round: the macro generates
some content, and the formatter adapts to it.
Btw, I still have the corresponding patch series aging on my laptop...
and I'd like to commit that. OK?