##// END OF EJS Templates
rhg: consistently use the command name given in clap::command!(<...>) macro...
rhg: consistently use the command name given in clap::command!(<...>) macro Before this patch there are 2 things the user controls: 1. the module/command name, specified in subcommand! macro 2. the command name, specified in clap::command! macro If these are out of sync, we get no compile error or a clear runtime error, but instead a confusing behavior where command line parser parses one thing, but running it doesn't work. This commit makes the clap::command! macro the sole authority determining the command name, so we don't have to worry about this weird behavior any more. It also makes it easy to validate agreement between (1) and (2) if we want it, but I didn't add the check because I'm not sure people necessarily want it.

File last commit:

r53299:6673cec8 default
r53420:021c1b16 default
Show More
Cargo.toml
4 lines | 108 B | application/toml | TOMLLexer
Gregory Szorc
rust: implementation of `hg`...
r35587 [workspace]
Raphaël Gomès
rust: add PyO3 based Rust extension module...
r53299 members = ["hg-core", "hg-cpython", "hg-pyo3", "rhg"]
Gregory Szorc
hgcli: add stub PyOxidizer project...
r45128 exclude = ["chg", "hgcli"]
Raphaël Gomès
rust: add explicit resolver field to top-level cargo manifest file...
r52014 resolver = "2"