From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml List <caml-list@inria.fr>
Subject: [Caml-list] Feedback on cmdliner doc language changes
Date: Tue, 31 Jan 2017 13:22:46 +0100 [thread overview]
Message-ID: <85CAE7D2449149BC942674B5F2685859@erratique.ch> (raw)
Hello,
The current cmdliner manual doc language is broken beyond hope. The next release is going to fix that which may break the rendering of some manpages [1]. Your feedback on the changes and new language definition is welcome:
https://github.com/dbuenzli/cmdliner/blob/08be600c4b7f00c08339f078a88b30234d84fc44/CHANGES.md#doc-language-sanitization
https://github.com/dbuenzli/cmdliner/blob/master/src/cmdliner.mli#L755-L768
Discussion can happen here:
https://github.com/dbuenzli/cmdliner/issues/68
Best,
Daniel
[1] I suspect most will not. But if:
git grep '\$([ib],[^)]*\$([mt]name)[^)]*)'
exits with 0 in your project you are affected for sure. Simply replace these marked up $(b,$(tname)) and $(b,$(mname)) by the variables $(tname) and $(mname) themselves.
reply other threads:[~2017-01-31 12:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85CAE7D2449149BC942674B5F2685859@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).