Titus

> does not look properly formatted. What doesn’t look proper? How would it look proper? Why do you write pretty markup, format it, and then not use optional tags? Fine...

AST transforms and formatters are not for small changes. If you want to lint and do small changes, such as that example, write your *own* plugins, using the positional info...

Right, your actual use case needs a code generator. And you want it pretty, so a formatter. That other use case where you only change some attributes of some elements,...

You don’t need utilities to do that. unified, and this plugin, run on fragments too. Not only on whole documents. You’re using `hastscript` etc already, right? So you have some...

> it will be already dirty on load. This sounds like an XY problem. You use two tools. Both tools format many things differently. One thing is indent. If you...

Closing as what the OP wants—no indent ever—[can be done now](https://github.com/syntax-tree/hast-util-format/releases/tag/1.1.0). By passing `indent: ''` or `indent: 0`. I don’t think it’s a good idea, to support what was asked...

Could you expand on this? Such as with an input (`readme.md`) / output (`LICENSE`) example?

I’m especially interested in what you’d like now, and what you’d like somewhere in the far away future!

From you second comment, what do you expect to happen now (not the future), if `ISC © author` is in the README?

Well that one makes sense, yes, but I was kinda looking for how long the list of supported (for now) licenses should be! Just supporting MIT (and/or ISC) is a...