It sounds like it would be a good idea to have test?

I'm just about to push it!

That test definitely fails on trunk

(But maybe wrap_mod could be renamed into wrap_in_module to avoid the confusion completely.)

Actually, the typo was the other way around - @diml mistyped wrap_mod which is the actual argument name. It reads to me as though Wojciech intended "wrap module" in 2012 when he added #mod_use.

I agree that a labelled argument or renaming would be better, but that code was fine for 8 years prior to being poked for a new feature - and the toplevel is getting a lot of attention elsewhere at the moment, anyway.

The use of false in #use_output is correct - otherwise it'll create an illegal module called (stdin), I think.

Yes, our comments on wrap_mod agree. (Although I see why it's confusing that I'm commenting on the diff from the other PR). Personally I would prefer to improve the code now that there was a bug, instead of waiting for the next bug. I will push a labeling commit.

I can confirm that a30e621 fixes the various topfind compilation issues I saw.

@dra27 I will let you decide if/when to merge given that I was the last to push a commit.

PR looks good to me too!

Thanks @diml - let's do it!