Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'task log' to commands processed by on-modify hook #17

Open
a7hybnj2 opened this issue May 31, 2018 · 5 comments
Open

Add 'task log' to commands processed by on-modify hook #17

a7hybnj2 opened this issue May 31, 2018 · 5 comments
Labels
enhancement New feature or request

Comments

@a7hybnj2
Copy link

Add functionality to the hook to track “task log start:### end:### description”

Use case: after a phone call I like to add it to the log including a start and stop time. Would be nice if this could also show up on the timew summary.

@lauft lauft changed the title Task log Add 'task log' to commands processed by on-modify hook Jun 1, 2018
@lauft lauft added the enhancement New feature or request label Jun 1, 2018
@a7hybnj2
Copy link
Author

a7hybnj2 commented Jun 1, 2018

In my initial playing around with hooks I don't think on-modify fires on 'task log' it does appear to fire 'on-add' however.

@pbeckingham
Copy link
Member

That makes sense, 'task log' is just 'task add' with an implicit 'status:completed'.

@lauft
Copy link
Member

lauft commented Jun 4, 2018

Does task log trigger any hook at all?
If not, we need to defer this issue to taskwarrior as well if such a feature is feasible.
In any case we need a new hook script which then triggers the appropriate timewarrior actions (I guess it just a simple timew track <start> - <end>).

@a7hybnj2
Copy link
Author

a7hybnj2 commented Jun 4, 2018

Yes, 'task log' appears to fire 'on-add' as I mentioned previously. I haven't had the time to do much testing beyond that.

@ChargingBulle
Copy link

I do this quite often too. It's abuse of the start tag and it doesn't function at all but it "feels like it should" work.
Because TimeWarrior and TaskWarrior get so easily out of sync I sometimes perform a task log on something immeditately after having done a timew track on it.

Example usage:

timew track 10:00 - 12:00 do the thing
&& task log start:10:00-1d end:12:00-1d do the thing
&& task 123 annotate "Mailed [email protected] at 11:46, absence autoresponse"

Right now I don't know how to perform an operation on +LATEST. Usually I look up the next ID via ids or in case of logged events, perform two action steps.

Having a task for it is useful. I frequently filter through completed tasks via the completed report.
task comp dog vac for when the dog was vaccinated last time (example).

(Not useful semi-rant) The overall problem is, of course, that task and taskw are completely different projects and they don't incorporate that well (task only interacts with timew like half ot the time, never syncs after an edit, timew doesn't know about tasks and can't sum time for a task, doesn't know about projects, ... etc the list goes on. It's almost like the tools hate each other and don't want to cooperate).

@lauft lauft transferred this issue from GothenburgBitFactory/timewarrior Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants