Open stephenmckinney opened 11 years ago
Yeah, we need 'pomo stop'. Now I use this script to kill the running pomo.
kill -9 $(ps aux | awk '/bin\/pomo/ {print $2}') 2> /dev/null
sed 's/running: true/running: false/g' ~/.pomo > ~/.pomo_temp
mv ~/.pomo_temp ~/.pomo
echo '#[default]#[fg=green]00:00#[default]' > ~/.pomo_stat
Good point on reseting ~/.pomo_stat
. I updated the ticket.
I'd like to write a pid file on fork and use that to kill the process, I just haven't had time to code it up. A pomo pause
would be great too.
With pomo pause
it would then be also possible to count the interruptions for a particular pomo.
+1 for stop or pause functionality
Unless there are any objections, I am going to make pomo run exclusively as a background process and eliminate pomo start --progress
. This will make this feature much easier to implement and it seems no one is using it as a foreground process anyway.
Well, yes I am using it ... on Windows, gasp, as Ruby lacks native fork support there and running in foreground is a nice workaround.
Having said that, go ahead and kill --progress
as I'd rather see tomato support first. I can come up with a hack for Windows later.
Stopping a task should include:
false
~/.pomo_stat
to#[default]#[fg=green]00:00#[default]
Possible option for maintaining processes: https://github.com/rjackson/singleton_process