daf6732368
The previous cleanup defined long help separately from the usage text generated by cmdargs. This meant keeping flag descriptions synced between the two, and also the short help was often too verbose and longer than the long help. Now, the non-usage bits of long help are defined as pre and postambles within the cmdargs mode, letting cmdargs generate the long help including all flags. We derive the short help from this by truncating at the start of the hledger common flags. Most of the bundled addons (all but hledger-budget) now use the new scheme and have pretty reasonable -h and --help output. We can do more to reduce boilerplate for addon authors. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| aliases.sh | ||
| budget-rewrite.sh | ||
| compile.sh | ||
| csv.mk | ||
| hledger-autosync | ||
| hledger-budget.hs | ||
| hledger-chart.hs | ||
| hledger-check-dates.hs | ||
| hledger-dupes.hs | ||
| hledger-equity.hs | ||
| hledger-print-unique.hs | ||
| hledger-register-match.hs | ||
| hledger-rewrite.hs | ||
| README | ||
hledger add-on commands, hledger-related scripts, developer builds. Scripts named hledger-* are hledger add-on commands. The ones in this bin/ directory are tested along with hledger, but shipped as add-ons rather than built-in commands because they are experimental, or for some other reason. Add this directory to your $PATH and they will show up as commands listed by hledger (or, you can run them directly). To speed them up (recommended), compile them: $ bin/compile.sh When using hledger to run add-on commands, remember to use a -- before add-on-specific options or hledger will complain. Like so: $ hledger [HLEDGEROPTS] ADDONCMD [-- ADDONOPTS] See also http://hledger.org/hledger.html#add-on-commands . hledger-related bash scripts, example make rules etc. are also kept here. And hledger developer binaries may get stored here, such as old versions for benchmarking, and platform-specific binaries.