fniessink / next-action Goto Github PK

Show which file the next action was selected from somehow, e.g.:

$ next-action --file work.txt home.txt
(A) Fix leaking roof [home.txt]

$ next_action -n3 # Or --number 3
(A) World peace
(B) End hunger
Call mom @home

A configuration file, written in Python, could contain a mapping of contexts to Boolean functions that return True if the context is applicable, False otherwise.

For example:

contexts = {
    "@night": lambda: 18 <= datetime.datetime.now().hour <= 23,
    "@work": lambda: requests.get("http://ipinfo.io").json()["city"] == "Amsterdam"
}

$ next_action -@work
(B) Work out

Or maybe

$ next_action not @work
(B) Work out

Should this be an option? Default on/off?

Since tasks will usually belong to a single project, it doesn't make sense to require the next action to belong to all projects specified. So, the next action is a task that belongs to at least one of the specified projects.

$ next-action +GarageSale +SpringCleaning
Clean out the garage +GarageSale

If a context is specified as well, then the next action should have that context:

$ next-action +GarageSale +SpringCleaning @home
Dry clean curtains +SpringCleaning @home

Separate colors for priority, contexts, projects, dates, and key-value pairs. Options:

• Blessings in concert with Colorama for implementation
• Pygments/Pygmentize has support for todo.txt

$ next-action --priority C --all
(A) Call mom
(B) Write proposal for client
(C) Buy beer
(C) Lose weight

Giving no priority would amount to --priority Z. --no-priority would pick the next action from tasks without priority.

A task with a creation date should come before a task without a creation date, all other things equal.

Tasks with future creation dates are already ignored.

Flatten e.g {'number': ["must be of ['integer'] type"]} to number must of be integer type and {'file': [{0: ['must be of string type']}]} to file item 0 must be of string type.

Possible solution: https://pypi.org/project/ConfigArgParse/

The bot created this issue to inform you that pyup.io has been set up on this repo.
Once you have closed it, the bot will open pull requests for updates as soon as they are available.

$ cat todo.txt | next-action -
Buy newspaper

Use the fileinput module for iterating over the files, including stdin.

Currently, a Python traceback is shown.

number: 3

or

all: True

Note that if the config file has number: 3, specifying --all on the command line should overwrite it.

http://docs.python-cerberus.org/en/stable/

Due dates are not part of the todo.txt spec, but are usually added using the key:value pattern, e.g.:
Pay taxes due:2018-05-01

• Move development dependencies to requirements-dev.txt
• Add wheel format to uploaded distributions.

$ next-action -f todo.txt -f big-project.txt 
(B) Review proposal [big-project.txt]

Options: always, never, when reading multiple files (default)

Select a next action that is over due:

$ next-action --over-due
Buy flowers due:2018-02-14

Show all overdue next actions:

$ next-action --all --over-due
Buy flowers due:2018-02-14
Submit taxes due:2018-05-01

The help info and examples should be generated to prevent typo's and inconsistencies.

Maybe --version should do this?

$ next-action --version
next-action 0.16.0
next-action 0.17.0 is available; install with "pip install --upgrade next-action"

$ next action
Buy present for dad

$ next_action done
Give present to dad

This feature would entail changing the todo.txt, which none of the other features do so far.

Instead of [@CONTEXT [@CONTEXT ...]] [+PROJECT [+PROJECT ...]] [-@CONTEXT [-@CONTEXT ...]] [-+PROJECT [-+PROJECT ...]]

Have something like [ [-]@CONTEXT | [-]@PROJECT ] ...

Or even switch from positional arguments to optional arguments:

-i @CONTEXT | +PROJECT, --include @CONTEXT | +PROJECT
-x/-e @CONTEXT | +PROJECT, --exclude @CONTEXT | +PROJECT

Tasks with a start date in the future can't be the next action (yet).

$ next-action @home
(A) Install smoke detectors @home

While tasks usually belong to one project, they will often have multiple contexts. So the next action should typically have all specified contexts.

$ next_action @work @lunch
Eat fruit @lunch @work and @home