Daniel Bünzli

Note when I meant upstream, I meant upstream in `ocaml` not in `js_of_ocaml`. In general I think we are not well served by the toploop APIs upstream and that's where...

Yes I thought this would quickly show up and I didn't do anything because I had no good answer to it yet. I'm also not very happy about the procedure...

> How about a carcass install that could be managed by OPAM and not in ~/.carcass at all? Not sure what you mean by that. I don't really want to...

Taking inspiration of what was done in `odig` I think a good scheme for this would be the following. We add a notion of `$CARCASS_ROOT`, this will typically be `$(opam...

Yes it would be nice. I thought a little bit about this when I did the environment variable support but the right design is not self-evident when you take into...

The current status isn't ideal but I wouldn't say it's that bad either. I'm not sure I really understand your objection about Option 1. AFAIR ([here](https://github.com/b0-system/brzo/blob/master/src/brzo.ml)) it works since *required*...

> Its unusual but fairly useful since we can have a few required arguments that are mostly constant (e.g. a path to some other utility/script), which is tedious to specify...

There are certainly many different workarounds (e.g. process your `Sys.argv` before giving it to `Cmdliner`) and I don't have the feeling that's a "pretty common thing to want". I'm not...

What's your use exactly ? Can you use `Cmd.name` instead ?

> Well, I found the message confusing It is ! I was just wondering whether it was ok for you to you not to act on `Cmd.info` but `Cmd.t` instead.