Simon Michael

the built-in help flag is hard to customise

1

I'd like to make -h a synonym for --help, and suppress -?. But "h" is automatically assigned to another flag (--hide-successes). If I add the "explicit" annotation to that one,...

modeHelp eats blank lines

1

I have a mode-building helper that wants to show multiple blank-line-separated paragraphs of help text, above the cmdargs-generated flags/subcommands help. This means using modeHelp, not modeHelpSuffix, but it seems blank...

expandArgsAt doesn't understand ~

1

expandArgsAt and @ARGSFILE seems a great feature, which I've enabled in hledger 1.4. I notice that @~/some/file doesn't work though, you have to write @$HOME/some/file instead. Perhaps there is some...

an optional value is not parsed as part of the option if separated from the flag by a space

1

Eg https://github.com/simonmichael/hledger/issues/149 .

ghc-mod fails in a multi-package stack project

6

`ghc-mod check FILE` in the root of a multi-package stack project doesn't detect the stack package db. ``` $ ghc-mod check hledger-lib/Hledger/Read/JournalReader.hs hledger-lib/Hledger/Read/JournalReader.hs:101:8:Could not find module ‘Hledger.Data’Use -v to see...

allow comma in tag values [.]

8

Currently tag values can't contain a comma, as it's used to separate multiple tags on a line. We could disallow multiple tags per line, or allow commas within single/double-quotes (as...

hledger-ui should be able to read standard input

2

This should work: ``` ~/src/hledger$ echo $TERM xterm-256color ~/src/hledger$ cat examples/sample.journal | hledger-ui -f- hledger-ui: getTerminalAttributes: invalid argument (Bad file descriptor) ```

ledger-mode setup for hledger needs documenting

33

## --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36005395-ledger-mode-setup-for-hledger-needs-documenting?utm_campaign=plugin&utm_content=tracker%2F536505&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F536505&utm_medium=issues&utm_source=github).

[hledger-install.sh](https://github.com/simonmichael/hledger/blob/master/hledger-install/hledger-install.sh) uses any stack executable that's already installed. Fairly often that is too old and [fails](https://groups.google.com/d/msg/hledger/SWFV2n6xMQA/udNACGhOCgAJ). We need to check the stack version and do something helpful if it is...

some auto posting rule parse issues

1

``` 2018/1/1 (a) 1 = date:from 2018 b 1 $ hledger-1.9 -f a.j print --auto 2018/01/01 hledger-1.9: "date:from" gave a date parse error () ``` The date: query term fails...