Is there some shorthand or concise notation for requiring multiple sibling submodules? For example, I can require (require json net/url) pretty neatly, but I end up doing a lot of repetition with submodules like

(require web-server/templates
         (submod ".." replies)
         (submod ".." layouts)
         (submod ".." pages)
         (submod ".." logging))

It’s possible that I misunderstand how to do this idiomatically, however. Any suggestions or clarification appreciated.

@nathaniel does (submod “..” replies layouts pages logging) work?

@abmclin no, because that means that I am trying to drill down, as if logging was a child of pages: module name: #<resolved-module-path:(submod 'main[2565] replies layouts pages logging)>

Oh I see it’s really individual submod path elements rather than submod names

yeah so ".." replies means “go up a level and then down into replies”, or at least that’s how I think about it what I’d like to say is “go up a level and get then go down into foo, bar, and buzz”

@nathaniel Does multi-in work with submodules? If not that seems like a good feature request.