otremblay / jkl Goto Github PK

Ideally, jkl would allow reading a configuration from .config/jkl. While it is used predominantly for graphical applications, it is a recognized standard configuration file location.

Probably around here the logic could be changed to allow recursing through hidden folders, or specify that .config/jkl/config should be parsed

The program should be able to run non-interactively, in such a way that calls to jkl can be made part of a script. It's currently not the case (AFAIK, calling jkl with a file always call $EDITOR if found).

Moreover, the -f switch should accept - as a way to mean "standard input". And/or we should detect if something is piped to jkl to default to standard input processing.

It should be possible to move from one sprint to the next and/or to current sprint and/or repriorize within backlog.

We should use CI to automatically generate binary and source code releases.

Perhaps I can contribute to this.

Potential

• linked stories
• work log
• url to viewed jira ticket
• possible task transitions

Cuz they're nice.

The following command line invocations should trigger the help screen :

• jkl help
• jkl --help
• jkl -h ✅