Since find() will transform a user query from "find syntax" to a URI, it would be possible not the user does not want to "just open this URL" for a search or accessing a ressource, but to give this result to an other url, or again to find (also if the find result is not a URL, but a find query it self).
<symbol><engine>%20<query>
!m tokyo hotel
<symbol_N><engine_N>%20<query_N> | <symbol_N+1><engine_N+1>%20<query_N+1>
Could also explore the . "meta symbol prefix", if that works, or parenthesis followed by a symbol etc.
.>jsonapi<query>.+space<to html web components>.+qrcode<with content>
.>jsonapi(query).+space(to html web components).+qrcode(with content)
Since
find()will transform a user query from "find syntax" to a URI, it would be possible not the user does not want to "just open this URL" for a search or accessing a ressource, but to give this result to an other url, or again to find (also if the find result is not a URL, but a find query it self).<symbol><engine>%20<query> !m tokyo hotel <symbol_N><engine_N>%20<query_N> | <symbol_N+1><engine_N+1>%20<query_N+1>Could also explore the
."meta symbol prefix", if that works, or parenthesis followed by a symbol etc.