mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-09-05 04:57:21 +02:00
Just set contextTask in Task::modify
Based on the observation that every command was setting contextTask immediately before calling `task.modify(..)`.
This commit is contained in:
parent
db26a28bf9
commit
2ea6dd627e
11 changed files with 5 additions and 42 deletions
|
@ -30,8 +30,6 @@
|
|||
#include <format.h>
|
||||
#include <main.h>
|
||||
|
||||
extern Task* contextTask;
|
||||
|
||||
////////////////////////////////////////////////////////////////////////////////
|
||||
CmdAdd::CmdAdd ()
|
||||
{
|
||||
|
@ -56,7 +54,6 @@ int CmdAdd::execute (std::string& output)
|
|||
|
||||
// the task is empty, but DOM references can refer to earlier parts of the
|
||||
// command line, e.g., `task add due:20110101 wait:due`.
|
||||
contextTask = &task;
|
||||
task.modify (Task::modReplace, true);
|
||||
Context::getContext ().tdb2.add (task);
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue