A command-line task manager
Best Laid Plans
The dstask personal tracker lets you manage your to-do list from the command line. Dstask uses Git version control to store tasks, letting you synchronize your to-do list across multiple devices.
After finding a much-needed network cable under a pile of junk in the basement, I decided it was time to add cleaning up the basement to my to-do list. To manage personal tasks (even unpleasant ones like this), the dstask personal tracker can help you prioritize tasks and track completion.
Unlike many other task managers, dstask exclusively runs on the command line. With a short and succinct command, you can add a new task or mark off a completed one. On request, dstask provides a list of all pending tasks, sorted by urgency. Filters help you stay on track in the task jungle. As an added benefit, you can use your task list to show customers or your boss your completed work.
Under the hood, dstask stores the pending tasks in the Git version management system, letting you sync tasks across all your devices. However, unlike dstask's other features, synchronization requires some Git know-how.
Kickstart
To get dstask up and running, first install Git using your package manager. To install Git on Ubuntu, type:
sudo apt install git
Next, go to the dstask project page on GitHub [1] and click on the current version number on the right below Releases. Under Assets, download the version for Linux, dstask-darwin-amd64
.
Rename the resulting program dstask
and make it executable. To do this, run:
chrmod +x dstask
You do not have to actually install dstask, but the developer does recommend storing dstask in /usr/local/bin
, which lets all of the system's users call the program directly by typing dstask
.
After that, you still have to create the Git repository where dstask stores all the tasks and become acquainted with Git (Listing 1). Replace editorial@linux-user.en
and Tim Sch¸rmann
with your own email address and full name. Without this information, you will always get error messages when working with dstask.
Listing 1
Creating a Git Repository
$ mkdir ~/.dstask && git -C ~/.dstask init $ git config --global user.email "editorial@linux-user.en" $ git config --global user.name "Tim Sch¸rmann"
Come On In
To add the basement cleanup task to dstask, use the call shown in line 1 of Listing 2. The add
command tells the program to create a new task, which is described in the following brief summary (clean up basement
).
Listing 2
Adding Tasks
01 $ dstask add clean up basement +basement +private P2 02 $ dstask add +private basement +clean up basement P2
Dstask adds all words that follow a plus sign (+
) to the task as keywords (i.e., basement
and private
in Listing 2). These tags will help you later on when searching for a specific task. You can also add the tags to the summary, as shown in line 2 of Listing 2.
In addition, you can set the task priority, which is shown by the number following P
. Dstask supports priority levels P3
to P0
, with P0
for urgent tasks and P2
for normal priority tasks. In Listing 2, I've set my basement cleanup task to P2
, since it's not time critical. Dstask automatically defaults to P2
if you don't include the priority level.
Roll Up Your Sleeves
To see what dstask has on your to-do list, just call dstask
. The program assigns a consecutive ID to each task. Entering dstask 1
shows detailed information about the task (Figure 1). Dstask ignores case sensitivity in the tags.
The detailed information also shows the task status
. Immediately after creation, the task will be shown as pending
. When you head down to the basement and pick up the first box, call
dstask start clean up basement
to change the status. This switches the task to the active
state, signifying that the task is in progress. If you take a break, stop processing with
dstask stop clean up basement
which toggles the task back to the pending
state.
Once the basement is finally clean, mark the task as done by entering
dstask done clean up basement
Even though dstask is done reminding you about this task, it will still store the task, thereby creating a record of your completed tasks for your boss or client.
To get a report on all completed tasks, enter
dstask show-resolved
Dstask automatically sorts the tasks by weeks. If you want to remove a task from the dstask repository, use the following command:
dstask remove clean up basement
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Gnome 47.1 Released with a Few Fixes
The latest release of the Gnome desktop is all about fixing a few nagging issues and not about bringing new features into the mix.
-
System76 Unveils an Ampere-Powered Thelio Desktop
If you're looking for a new desktop system for developing autonomous driving and software-defined vehicle solutions. System76 has you covered.
-
VirtualBox 7.1.4 Includes Initial Support for Linux kernel 6.12
The latest version of VirtualBox has arrived and it not only adds initial support for kernel 6.12 but another feature that will make using the virtual machine tool much easier.
-
New Slimbook EVO with Raw AMD Ryzen Power
If you're looking for serious power in a 14" ultrabook that is powered by Linux, Slimbook has just the thing for you.
-
The Gnome Foundation Struggling to Stay Afloat
The foundation behind the Gnome desktop environment is having to go through some serious belt-tightening due to continued financial problems.
-
Thousands of Linux Servers Infected with Stealth Malware Since 2021
Perfctl is capable of remaining undetected, which makes it dangerous and hard to mitigate.
-
Halcyon Creates Anti-Ransomware Protection for Linux
As more Linux systems are targeted by ransomware, Halcyon is stepping up its protection.
-
Valve and Arch Linux Announce Collaboration
Valve and Arch have come together for two projects that will have a serious impact on the Linux distribution.
-
Hacker Successfully Runs Linux on a CPU from the Early ‘70s
From the office of "Look what I can do," Dmitry Grinberg was able to get Linux running on a processor that was created in 1971.
-
OSI and LPI Form Strategic Alliance
With a goal of strengthening Linux and open source communities, this new alliance aims to nurture the growth of more highly skilled professionals.