Gabriel Scherer
Gabriel Scherer
Thanks! I don't need write commit to your fork (I can fetch your fork and resubmit a PR if need be, which sounds cleaner); it just landed in the middle...
My preference would be to not use `mustache` to avoid conflict with the semi-standard Ruby implementation. I don't have much of a preference as to which name to use (my...
(For context, we are talking about issue #61, "Consider changing the binary name".) I guess `mustache-cli` is also an option, but it's weird as it is both different and completely...
(Thanks for the packaging work!)
The CI fails on this PR: ``` - File "mustache-cli/dune", line 10, characters 7-15: - 10 | (run mustache --help=groff))) - ^^^^^^^^ - Error: Program mustache not found in the...
Sounds like a good plan... especially if I'm not the one doing the work.
> The question is, where would this library live? No strong opinions here. If you and @mransan are willing to maintain it, it could live in the same source repository...
In fact, explicitly giving `intros H1 H2.` works badly even if the correct number of variables are given, because it disturbs the fresh-name generation later in the script to reuse...
I'm impressed that you dared implement this change, thanks! This is impressive. For the ease of reviewing, could you maybe split the first commit between the implementation change and the...
@Octachron in https://github.com/ocaml/ocaml/issues/6634#issuecomment-1286642883 you show an example message: ``` Error: Signature mismatch: Modules do not match: sig type t = [ `T of t ] end is not included in...