Python库 | next-action-1.5.0.tar.gz

# Next-action [](https://pypi.org/project/next-action/) [](https://pyup.io/repos/github/fniessink/next-action/) [](https://travis-ci.com/fniessink/next-action) [](https://www.codacy.com/app/frank_10/next-action?utm_source=github.com&amp;utm_medium=referral&amp;utm_content=fniessink/next-action&amp;utm_campaign=Badge_Grade) [](https://www.codacy.com/app/frank_10/next-action?utm_source=github.com&utm_medium=referral&utm_content=fniessink/next-action&utm_campaign=Badge_Coverage) [](https://sonarcloud.io/api/project_badges/measure?project=fniessink%3Anext-action&metric=alert_status) Determine the next action to work on from a list of actions in a todo.txt file. Don't know what *Todo.txt* is? See <https://github.com/todotxt/todo.txt> for the *Todo.txt* specification. *Next-action* is not a tool for editing todo.txt files, see <http://todotxt.org> for available options. ## Table of contents - [Demo](#demo) - [Installation](#installation) - [Usage](#usage) - [Limiting the tasks from which next actions are selected](#limiting-the-tasks-from-which-next-actions-are-selected) - [Showing more than one next action](#showing-more-than-one-next-action) - [Task dependencies](#task-dependencies) - [Styling the output](#styling-the-output) - [Configuring *Next-action*](#configuring-next-action) - [Option details](#option-details) - [Recent changes](#recent-changes) - [Developing *Next-action*](#developing-next-action) - [Installing the development environment](#installing-the-development-environment) - [Running unit tests](#running-unit-tests) - [Running quality checks](#running-quality-checks) ## Demo  ## Installation *Next-action* requires Python 3.6 or newer. `pip install next-action` ## Usage ```console $ next-action --help Usage: next-action [-h] [--version] [-c [<config.cfg>] | -w] [-f <todo.txt> ...] [-r <ref>] [-s [<style>]] [-a | -n <number>] [-d [<due date>] | -o] [-p [<priority>]] [--] [<context|project> ...] Show the next action in your todo.txt. The next action is selected from the tasks in the todo.txt file based on task properties such as priority, due date, and creation date. Limit the tasks from which the next action is selected by specifying contexts the tasks must have and/or projects the tasks must belong to. Optional arguments: -h, --help show this help message and exit --version show program's version number and exit Configuration options: -c [<config.cfg>], --config-file [<config.cfg>] filename of configuration file to read (default: ~/.next-action.cfg); omit filename to not read any configuration file -w, --write-config-file generate a sample configuration file and exit Input options: -f <todo.txt>, --file <todo.txt> filename of todo.txt file to read; can be '-' to read from standard input; argument can be repeated to read tasks from multiple todo.txt files (default: ~/todo.txt) Output options: -r {always,never,multiple}, --reference {always,never,multiple} reference next actions with the name of their todo.txt file (default: when reading multiple todo.txt files) -s [<style>], --style [<style>] colorize the output; available styles: abap, algol, algol_nu, arduino, autumn, borland, bw, colorful, default, emacs, friendly, fruity, igor, lovelace, manni, monokai, murphy, native, paraiso-dark, paraiso-light, pastie, perldoc, rainbow_dash, rrt, tango, trac, vim, vs, xcode (default: None) Show multiple next actions: -a, --all show all next actions -n <number>, --number <number> number of next actions to show (default: 1) Limit the tasks from which the next actions are selected: -d [<due date>], --due [<due date>] show only next actions with a due date; if a date is given, show only next actions due on or before that date -o, --overdue show only overdue next actions -p [<priority>], --priority [<priority>] minimum priority (A-Z) of next actions to show (default: None) @<context> ... contexts the next action must have +<project> ... projects the next action must be part of; if repeated the next action must be part of at least one of the projects -@<context> ... contexts the next action must not have -+<project> ... projects the next action must not be part of Use -- to separate options with optional arguments from contexts and projects, in order to handle cases where a context or project is mistaken for an argument to an option. ``` Assuming your todo.txt file is your home folder, running *Next-action* without arguments will show the next action you should do. Given this [todo.txt](https://raw.githubusercontent.com/fniessink/next-action/master/docs/todo.txt), calling mom would be the next action: ```console $ next-action (A) Call mom @phone ``` The next action is determined using priority. Due date is considered after priority, with tasks due earlier getting precedence over tasks due later. Creation date is considered after due date, with older tasks getting precedence over newer tasks. Finally, tasks that belong to more projects get precedence over tasks that belong to fewer projects. Several types of tasks can not be a next action: - completed tasks (~~`x This is a completed task`~~), - tasks with a creation date in the future (`9999-01-01 Start preparing for five-digit years`), - tasks with a future threshold date (`Start preparing for emigration to Mars t:3000-01-01`), and - blocked tasks (see [task dependencies](#task-dependencies) below). ### Limiting the tasks from which next actions are selected #### By contexts and/or projects You can limit the tasks from which *Next-action* picks the next action by passing contexts and/or projects: ```console $ next-action @work (C) Finish proposal for important client @work $ next-action +DogHouse (G) Buy wood for new +DogHouse @store $ next-action +DogHouse @home Get rid of old +DogHouse @home ``` When you supply multiple contexts and/or projects, the next action belongs to all of the contexts and at least one of the projects: ```console $ next-action +DogHouse +PaintHouse @store @weekend (B) Buy paint to +PaintHouse @store @weekend ``` It is also possible to exclude contexts, which means the next action will not have the specified contexts: ```console $ next-action +PaintHouse -@store Borrow ladder from the neighbors +PaintHouse @home ``` And of course, in a similar vein, projects can be excluded: ```console $ next-action -+PaintHouse @store (G) Buy wood for new +DogHouse @store ``` If no tasks match the combination of tasks and projects, it's time to get some coffee: ```console $ next-action +DogHouse @weekend Nothing to do! ``` But, if there's nothing to do because you use contexts or projects that aren't present in the todo.txt file, *Next-action* will warn you: ```console $ next-action +PaintGarage @freetime Nothing to do! (warning: unknown context: freetime; unknown project: PaintGarage) ``` #### By due date To limit the the tasks from which the next action is selected to actions wi