[TS-16] allow tasksh to use CLI arguments on launch #15
Labels
enhancement
New feature or request
Milestone
Comments
|
Migrated metadata: |
|
Cory Donnelly on 2015-12-30T19:12:26Z says: This is in direct conflict with TS-22 -- David is suggesting that tasksh would perform operations described by CLI arguments and remain within the shell, while prior to v1.1.0, tasksh would perform operations passed as CLI arguments and then quit. I prefer David's suggestion. |
|
Paul Beckingham on 2016-09-06T12:13:26Z says: With TS-29 it's getting closer. Now it accepts newline-separated input piped in, but quits after. |
ThomasAdam
added a commit
to ThomasAdam/taskshell
that referenced
this issue
Jun 21, 2018
When invoking tasksh with command line arguments, it's useful to try and process these via taskwarrior so that: tasksh pro:home list would output the appropriate tasks before displaying the prompt. To achieve this, refactor some of the setup calls to generate the prompt, as well as refactoring the commandLoop. Fixes GH issue GothenburgBitFactory#15
ThomasAdam
added a commit
to ThomasAdam/taskshell
that referenced
this issue
Jul 13, 2018
When invoking tasksh with command line arguments, it's useful to try and process these via taskwarrior so that: tasksh pro:home list would output the appropriate tasks before displaying the prompt. To achieve this, refactor some of the setup calls to generate the prompt, as well as refactoring the commandLoop. Fixes GH issue GothenburgBitFactory#15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
David Patrick on 2014-12-23T13:22:18Z says:
It would be a Good Thing(tm) if one could launch the task shell using arguments, as in;
which would open tasksh, and run immediately the long report with [pro:foo and +bar] filter
The text was updated successfully, but these errors were encountered: