Something went wrong. Try again.
How a command-line program ends
Something went wrong. Try again.
ocaml-cli-exit cli-exit.opam
1.6 kB · 46 lines
at main
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647# This file is generated by dune, edit dune-project insteadopam-version: "2.0"synopsis: "Exit statuses and closed-pipe handling for cmdliner programs"description: """The main function of a cmdliner program, with the process-level end of arun in one place: the SIGPIPE disposition, the status the evaluation answers,the report for an exception nothing expected, and the quiet end when thereader of a pipeline leaves. An operator pipes a listing into head, grep -q oran awk that stops at the line it wanted, and every one of those closes thepipe while there is still output to write. That is the ordinary end of apipeline rather than a fault in the writer, and a program that answers it withan internal error and exit 125, or dies of SIGPIPE with 141, teaches itsoperator to ignore the word error."""maintainer: ["Thomas Gazagnaire <thomas@gazagnaire.org>"]authors: ["Thomas Gazagnaire"]license: "ISC"tags: ["org:blacksun" "command-line-utilities" "area:10010862"]homepage: "https://tangled.org/gazagnaire.org/ocaml-cli-exit"bug-reports: "https://tangled.org/gazagnaire.org/ocaml-cli-exit/issues"depends: [ "dune" {>= "3.21"} "ocaml" {>= "5.1"} "cmdliner" "eio" "fmt" "alcotest" {with-test} "eio_main" {with-test} "mdx" {with-test} "odoc" {with-doc}]build: [ ["dune" "subst"] {dev} [ "dune" "build" "-p" name "-j" jobs "@install" "@runtest" {with-test} "@doc" {with-doc} ]]dev-repo: "git+https://tangled.org/gazagnaire.org/ocaml-cli-exit"x-maintenance-intent: ["(latest)"]