The vitrc variables %TASKID and (not even sure it exists) %TASKARGS is only mentioned peripherally in the man pages. I've been trying to use %TASKARGS (unsuccessfully) to address one of my long-standing pet-peaves; namely, that task filters (or arguments) are lost when I run a new report. This bugs me because I would like to look at a sub-set of tasks from different angles.
For the longest time, I clamored for more persistent filters, but then I realized that because I tend to start reports with custom key-bindings, I could make it behave as desired with custom-keybindings that include arguments. It might look like this, in my .vitrc;
David Patrick on 2015-08-17T22:06:13Z says:
The vitrc variables %TASKID and (not even sure it exists) %TASKARGS is only mentioned peripherally in the man pages. I've been trying to use %TASKARGS (unsuccessfully) to address one of my long-standing pet-peaves; namely, that task filters (or arguments) are lost when I run a new report. This bugs me because I would like to look at a sub-set of tasks from different angles.
For the longest time, I clamored for more persistent filters, but then I realized that because I tend to start reports with custom key-bindings, I could make it behave as desired with custom-keybindings that include arguments. It might look like this, in my .vitrc;
map=:minimal %TASKARGS
map =:ls %TASKARGS
but %TASKARGS isn't recognized.
how does that (could that) work?