lee/hpr-knowledge-base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update metadata and transcripts through end of July 2026

Browse Source 
Refreshed episodes/hosts/comments/series from hpr.sql, and added
official HPR transcripts for the 180 episodes aired since the last
sync (hpr4516-hpr4695).
This commit is contained in:
Lee Hanken
2026-07-31 16:18:57 +01:00
parent 37e8274bff
commit 087f80c44d
184 changed files with 61169 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
hpr_transcripts/hpr4549.txt
+91
View File
@@ -0,0 +1,91 @@
Episode: 4549
Title: [deprecated] Pomodoro Task Tool (pomotask.sh)
Source: https://hub.hackerpublicradio.org/ccdn.php?filename=/eps/hpr4549/hpr4549.mp3
Transcribed: 2026-07-31 16:13:45 (official HPR transcript)
---
This is Hacker Public Radio Episode 4549, for 2026-01-08
Today's show is entitled, "[deprecated] Pomodoro Task Tool (pomotask.sh)"
The host is candycanearter and the duration is 00:04:29
The flag is Clean, and the license is CC-BY-SA
The summary is "Going over a small bash script I used to use to help with tasks"
Hi, and welcome back to me making an episode.
So I figured making a bunch of episodes to a young or random scripts have made for myself
and making a sub-look would be fun in an easy way to get some episodes out.
The full script will be in the notes, and most of the time will be bash or Python.
This script, in particular, I had rewritten, as I dropped a swing app.
So that's why it's deprecated in the title.
And one of the sort on this script is follow up on my last episode of Creeping How Well Task
where you're tied in the scripts, and over here, this deprecated one that are starting
with page on a script, which is much more difficult to discuss.
I made a circle back to the job erosion of the script at the end of the series, so we're
forward to that, if it ever happened.
This program act as a simple preliminary timer, but also printed a path for each project
in your task where you're interested in sequence.
The sub-cell lot for someone like me, who always sounds the focus on the most critical tasks
for getting to work on blog tasks, which end up picking up on me.
So now, let's start the part of my line analysis.
L-Rest equal 0 is just a pressure that they counter for a 15-minute break on a third
loop and resetting it.
For this, I don't know if the way I found a drill timer work, if I get 25 minutes of work
at 5-minute break, except for that on the third break, it's a 15-minute break.
This variable will keep track of that, and the plan of 15-minute break on the third
break.
This next line is the program in an event loop, as the program is designed to run until
the user-turn agent.
This current statement is mostly just here for debugging and to show the user with status
to program it in.
The inner loop runs once for each project in your list and then returns back to the top
of the loop in order to get more projects.
This line is actually, I guess, from your task where you're interested, if you think
a lot of bash magic, so let's take this step by step.
The dark sign in brackets is the common syntax to find a sub-shel and run a command in it.
It's uncaptured the output of the command.
This invoke a man is at the heart of many bash scripts due to its profitability.
We're invoking task warrior with the filter of a plus pendinger, pending a virtual tag that
captures any tag of the pending status.
This isn't needed because by default, the unique command will capture any task in this
history, including completed, deleted, or waiting tasks.
A unique and a special scripting command at that print is all unique elements of the given
field.
It's output is then typed into shop, which then rearranges the line that randomly.
This inner portal then gives over each project that was captured and displays its tasks
in a table.
Once the inner portal runs out of projects to display, it then returns to the outer
portal to collect more, just like a command is another debug.
The error, or just rather than a command, that's the play it to the user.
Passplayer displayed an error code if the provided filter returns nothing, and the uses
to make it to display the entire table if a project is completely clear if the force
timer is up.
The double bars intact is another bash vote in, that says to run the second command if the
first one returns an error.
This line is a simple bash syntax that can be used in place of a statement.
This is more of a personal preference and can be removed if needed, but the first display
after it falls, like it will always display the full task table.
Here is what a task table is actually displayed if we're using two built-in bash programs
being time out, but sure makes a program after they give a number of seconds, and watch,
which continuously runs the provided command and displays this output to terminal.
This also lets you skip a given or superior if needed by a basic control C. This is
the only term that it's a watch program.
Then we increment the rest timer, then we prompt the user to begin a break by crossing
enter, which is done through a basic read command.
The rest time is done for the 5th and 5th at the standard break time, but if we've got
this read break so far, then the rest time right instead such a 15 in the chapter is reset.
Then we do a basic timer where we set up another while with, to check for when the rest
time is greater than 0, and then say for 60 seconds and then document the rest timer.
And then another prompt and read for the user to enter, to continue back to another
work, and then draw the end marker for the two loops we use in the beginning.
And that's it, the two and that's the loop to keep it running forever, as long as there
is still working on stuff. This is extremely rudimentary in half some issues, like how
some hospitals keep the right period, or how the first period each cycle is completely
discarded for showing a full table, but it worked pretty well for my use case, and
maybe we can have you all too.
You have been listening to Hacker Public Radio at Hacker Public Radio.org.
Today's show was contributed by a HPR listener like yourself.
If you ever thought of recording podcast, click on our upload link
to find out how easy it is.
Hosting for HPR has been kindly provided by an AnHonestHost.com, the Internet Archive,
rsync.net, and our mirror network.
Unless otherwise stated, today's show is released under a Creative Commons
Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.