neels@box:~$ ptimer -hGet the complete help with the -h option. |
neels@box:~$ ptimerJust call ptimer to get a status message. First invocation shows a grand total of zero hours. |
neels@box:~$ ptimer project_A Start a project timer by giving any name as argument to ptimer. The first query shows zero hours, which becomes "0:01" after one minute, for both "project_A" and the grand total. Stop the currently running project by passing "stop" to ptimer. The final total is 2 minutes. |
neels@box:~$ ptimer fooYou can also switch directly to another project, without stopping explicitly. |
neels@box:~$ ptimer log Calling ptimer log prints a log of each day and each month of project hours. Here, project "bar" is not included yet, since it is still running. Note that ptimer log also fixes the grand total if the log's total differs. So you can edit the log file at ~/.project-timer/log and then call ptimer log to calculate the new total. |
neels@box:~$ ptimer stopProject bar shows up in the log once its timer is stopped. |
neels@box:~$ ptimer foo This manually adds some hours to the running timer, here one hour and 23 minutes. Note: This is implemented by shifting the recorded starting time for this timer backwards by 1:23 hours. If you add many hours, the starting time may shift to the previous day. You can't add or remove time from stopped timers (short of editing the log file). Instead: start, then add, and stop again. |
neels@box:~$ ptimer -t -1:00This adjusts the grand total. Say you have submitted one working hour to your employer/client to appear on your paycheck. You can then adjust your running total like this. (This is an overall counter across all projects. It makes most sense when there is a single employer for all projects.) |
neels@box:~$ export PS1="\`cat ~/.project-timer/human-readable-state\` $PS1"Gimmick: include the timing status in your command prompt. |

