3/10/2024 0 Comments Edit tomato timer![]() This allows me to inspect my logs from my phone if needed. ![]() The way I, personally, use this, is to save my tomato logs inside a dropbox folder, which I keep synced on my phone. If this happens, you should cancel your tomato, and untomato the invalid log. Either your interruption is of the kind that you can quickly 'jot down' while the tomato is running, so that you can deal with it after the tomato has finished, or it is a significant interruption that has destroyed your current tomato as a unit of uninterrupted focus. I consider "pausing" a pomodoro interval to deal with interruptions, to defeat the whole point of the pomodoro technique. Obviously it is possible to do Ctrl-Z on a linux terminal (which effectively stops the ticking sound - fg will resume the sound), but this does not pause the timer itself. It is not currently possible to 'pause' the timer. You can press Ctrl-C while a tomato is running to terminate that tomato note that this does not remove the entry already logged (therefore this is also an easy way of adding a tomato to the log without having to complete the timer interval required) Type tomatoes to inspect the current state of your tomato log #Notes If no more entries remain, the logfile itself will be deleted Type untomato to remove the last entry from the log. If the log does not yet exist, this will simply exit with an error. Type, tomato by itself to log a tomato that repeats the previous description used (i.e. tomato Solving Math Problems to log a tomato with the description "Solving Math Problems" On apt based systems you can install these via sudo apt install gnome-shell-pomodoro sox Optionally, the gnome-pomodoro package, if you intend to use the default sound files I used, which were shamelessly stolen from gnome-pomodoro. The xtrlock package (a simple screen lock facility) The sox package (provides the 'play' function for playing audio files) Make the files tomato, tomatoconfig, tomatoes, and untomato executableĬopy them to /usr/local/bin (or simply add the directory containing these files to your PATH) #Installation instructionsĮdit the tomatoconfig file as appropriate It is a bare-bones pomodoro logger/timer, which forces you to launch each pomodoro interval separately in the terminal, and allows providing a description as an optional argument, thereby encouraging logging with minimal effort and thought. "how many pomodoros does this kind of task usually take?", "how many pomodoros can I usually do in a day?", "what kind of tasks take me more pomodoros than others (possibly for psychological reasons)", etc. This is very frustrating if you later want to use your pomodoro logs for planning, e.g. ![]() It's so easy to forget to do this, or simply not bother. However, this adds an extra layer of complexity with a gui app like gnome-pomodoro, since I need to remember to write something in my log, either before or after each pomodoro timer has completed. More importantly, I feel like my pomodoros are far more effective when I log them. ![]() I wanted something bare-bones for the terminal, so that I wouldn't have to deal with minimizing/maximizing windows and pressing start/stop buttons. I do most of my work (programming) on the terminal. I have used gnome-pomodoro happily so far, but I found it had the following features that I was missing: A pomodoro logger and timer for the terminal #Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |