<div dir="ltr"><div dir="ltr">Am Mi., 27. Juli 2022 um 12:04 Uhr schrieb Adam Sotona <<a href="mailto:adam.sotona@oracle.com">adam.sotona@oracle.com</a>>:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="en-CZ" style="overflow-wrap: break-word;">
<div class="gmail-m_-1532383809139238842WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">Unfortunately, “Prettyprinting” can be reduced to indentation and new lines only for XML and JSON, however YAML offers much more dynamic formatting.</span></p></div></div></blockquote><div><br></div><div>I have to admit that I never used YAML syntax in any form. Looking at the</div><div>Wikipedia page, it seems like YAML's optional "inline-style" corresponds</div><div>to the "single-line formatting" style of the prettyprinter approach, and its</div><div>indented multi-line blocks to multi-line formatting. In this case, the width</div><div>information passed up the tree would represent the "inline-style" width.</div><div><br></div><div>I would not rule out that it can be made to work. I agree with you that it</div><div>would entail more than just moving strings around, because printing</div><div>of lists and maps would have two distinct output modes. But it may</div><div>be possible to move the decision which mode to use out of the data</div><div>model.</div><div><br></div><div>-- mva</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="en-CZ" style="overflow-wrap: break-word;"><div class="gmail-m_-1532383809139238842WordSection1"><div><div><div>
</div>
</div>
</div>
</div>
</div>
</blockquote></div></div>