Jules Aguillon

This has been fixed by https://github.com/ocaml-ppx/ocamlformat/pull/957

Indeed, I tested too fast. I get this, which is wrong: ```ocaml (* 00000011111111112 * 45678901234567890 *) (* 1. xxxx x xxxx *) (* 2. xxxx xx xxxx *) (*...

I updated the list using the last release (0.13.0). Some are mysteriously fixed (not by fixing the linked issue) and one file has now a different bug (in `ocaml-variants`). I...

I ran ocamlformat over 80% of all opam packages. Error output: ``` ott.0.31/src/lex_menhir_pp.ml: formatting did not stabilize after 10 iterations. cil.1.7.3/src/ext/optutil.ml: ast changed. cil.1.7.3/src/ext/pta/olf.ml: ast changed. cil.1.7.3/src/ext/pta/golf.ml: ast changed. reason.3.6.0/formatTest/typeCheckedTests/input/comments.ml:...

The content of the original file is used during formatting to workaround loss of information in the parser. It is likely that the internals can't work with dummy locations, this...

OCamlformat uses the original string while formatting, so a function taking a channel wouldn't be interesting inside, it would entirely read the input before doing anything else. If it's just...

Sorry if my suggestion was wrong. Have you also tried modifying `Parse.ast` to avoid the string to lexbuf to string conversions ? The problem with attempting to call the wrong...

That's the formatting we expect, to separate the heavier syntax `{[` from the bigger piece of code. Perhaps the source can be changed to use `[ ... ]` instead, which...

Odoc doesn't follow ocamldoc in a lot of cases. Odoc is not sensitive to whitespaces around `{[` and `]}` and to the indentation of the whole block. It's reasonable to...

Here's a different idea: Do `fit-or-vertical` if at least an element of the "pipeline" is a call to an infix operator, `wrap` otherwise. Where "pipeline" is a chain of operators...