taskwarrior

Feature request

*** Clearly state the use case.

• What command did you run?
  task 275 modify due:tomorrow+1d

• What did you expect to happen?
  The usual:
  Modifying task 275 '…'.
  Modified 1 task.
  Project '…' is …% complete (x of y tasks remaining).

• What actually happened?
  No tasks specified.
  Indeed, the task 275 did not exist. It was 273. I may have been tired but I thought

And possibly Must* style methods.

This is necessary due to the ongoing development of a dstask web interface by @botto

The idea is that it would be super interesting to have another kind of isolation by using a local file in repositories. The idea is that, currently, we have only one planned way to isolate tasks: by using a persistent project name in the configuration. That allows to automatically list tasks based on the project set in the config. It’s also possible to use metadata filtering with the ls command,

Just like we do for filters and modifications, let's build some automatic documentation for the built-in report formats.

Pictures are often wonderful :-D sometimes it'd be nice to be able to figure out where the picture was taken and so on, a discrete link to the unsplash webpage would be great.