04:03 <dh`> grr why can't dune have actual documentation

04:04 <dh`> something I'm trying to work with runs dune with --no-buffer sometimes

04:04 <dh`> is this option mentioned in the man page? no.

04:04 <dh`> is this option mentioned in the section of the manual called "Command-Line Interface"? no

04:05 <dh`> it is only mentioned in passing in the FAQ section of the manual

04:05 <dh`> and that requires searching

04:21 <discocaml> <yawaramin> it's documented in `dune build --help`

04:25 <dh`> that is useful to know, but why isn't in the manual? and maybe the man page should include the options, or if not at least point to the --help

04:25 <dh`> s/isn't/isn't it/

04:27 <discocaml> <yawaramin> so, in the manual, the CLI section says: 'This is a short overview of the commands available in Dune. Reference documentation for each command is available through dune COMMAND --help.'

04:27 <discocaml> <yawaramin> i guess they don't want to repeat the same documentation in multiple places

04:28 <discocaml> <yawaramin> but the weird part is, imho, that the common options for all subcommands, like `dune build`, `dune exec`, are all repeated in the man pages of those subcommands, instead of being in the `dune --help` page

04:29 <discocaml> <yawaramin> and in the `dune --help` page the 'Common Options' section mentions only `--help` and `--version`, leading one to think that those are the only common options across all commands

04:29 <dh`> the manual I'm looking at (https://dune.readthedocs.io/en/stable/usage.html) contains no such text

04:30 <dh`> and there are ways to write the text once and include it in several places

04:30 <dh`> . o O ( or maybe there aren't because dune's so inflexible... )

04:30 <discocaml> <yawaramin> i'm looking at https://dune.readthedocs.io/en/stable/reference/cli.html

04:31 <discocaml> <yawaramin> imho, the 'common options' should be shown in `dune --help`, and the subommand help pages should just refer to that page

04:31 <dh`> ah I couldn't even find that page because it's mixed in with a collection of unrelated things with no ordering

04:32 <dh`> maybe usage.html should point to that page, too

04:36 <discocaml> <yawaramin> https://github.com/ocaml/dune/issues/11436

04:41 <discocaml> <yawaramin> yeah the dune docs grew organically and everybody added in bits and pieces in different places at different times

20:32 <dh`> documentation needs maintenance, possibly more so than code, and tends not to get it

20:32 <dh`> anyway I am trying to update a coq packaging and I'm having problems

20:33 <dh`> my understanding is that you're supposed to do dune build coq-core coq-stdlib coqide-server coqide, and after some misadventures I got that to run

20:34 <discocaml> <._null._> Do you want to install coq from source ?

20:34 <dh`> yes (see: "packaging")

20:35 <discocaml> <._null._> What do you want to package it for ?

20:36 <dh`> my understanding is that you're then supposed to use opam to install it, and the infrastructure I have does opaline -name $i -prefix $PREFIX _build/default/$i.install (for i in coq-core coq-stdlib coqide-server coqide)

20:36 <dh`> (plus some other args for path config and whatnot)

20:37 <dh`> (a) is that correct? and (b) actually running it causes it to try to call strip(1) on a python script, which of course fails and kills the whole thing

20:38 <discocaml> <._null._> I'm missing context;: I don't know opaline and I don't understand where python scripts come from

20:39 <dh`> so I suspect something in here is not actually the right incantation, but it's not clear what to change and documentation is pretty thin

20:39 <dh`> the python script is some coq thing

20:40 <dh`> "TimeFileMaker.py"

20:41 <discocaml> <._null._> You should ask on Coq's zulip for more knowledgeable people

20:42 <dh`> I was hoping this was an opam question and not a coq question

20:42 <discocaml> <._null._> If you want to do packaging yourself, I don't get why you would use opam

20:42 <dh`> because dune doesn't install things

20:42 <dh`> from what I can tell, this is the only way to install anything

20:43 <dh`> (other than writing it out by hand)

20:43 <discocaml> <._null._> Did you look into nix' and guix' scripts for opam packages ?

20:44 <discocaml> <._null._> (I presume they have packages for coq, where they replace opam)

20:44 <dh`> I am using a set of scripts for opam packages

20:44 <dh`> otherwise I'd probably be completely stuck right now, instead of partly

22:26 <dh`> oh well, I suppose it's time I figured out how to get zulip to work

23:09 <discocaml> <gooby_diatonic> I've been trying to get memtrace to work on 5.2.0+statmemprof with memtrace pinned to `https://github.com/dra27/memtrace#5_1_statmemprof`. In any case, the issue I had was when viewing the generated file, it says 0 bytes allocated. I was thinking it can either be because, 1, I didn't set it up correctly so the memprof API isn't working (which was initially what I was warned about when trying to install memtrace on 5.3.0), or that my pro