- 09 Apr, 2015 2 commits
-
-
Bram Schoenmakers authored
topydo edit won't work if EDITOR is unset
-
Jacek Sowiński authored
On some systems EDITOR is unset by default, so in such situation topydo would throw KeyError exception instead of opening todo.txt in vi.
-
- 31 Mar, 2015 3 commits
-
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
More output and behavior consistency between 'del', 'do', 'pri and 'postpone'
-
Bram Schoenmakers authored
Append parent contexts
-
- 28 Mar, 2015 2 commits
-
-
Jacek Sowiński authored
-
Jacek Sowiński authored
This works identically to append_parent_projects option. Code was generated by simply `s/project/context/`
-
- 26 Mar, 2015 7 commits
-
-
Jacek Sowiński authored
Adjust to changes introduced in: 3f096
-
Jacek Sowiński authored
1. Fail if *any* of supplied todo numbers is invalid 2. Print which todo numbers were invalid
-
Jacek Sowiński authored
pri: + We're now printing todo numbers in output + Test error output when any of supplied (multiple) todo IDs is invalid. both: + Test error output when *all* of supplied todo IDs are invalid
-
Jacek Sowiński authored
-
Jacek Sowiński authored
-
Jacek Sowiński authored
Show 'Invalid todo number: {number}.' messages also when *all* of supplied todo numbers are invalid. Before this commit it were returning synopsis in such situation.
-
Jacek Sowiński authored
-
- 24 Mar, 2015 1 commit
-
-
Bram Schoenmakers authored
Give 'postpone' command possibility to work with multiple todos
-
- 23 Mar, 2015 3 commits
-
-
Jacek Sowiński authored
-
Jacek Sowiński authored
-
Jacek Sowiński authored
topydo will report which todo IDs ('numbers') were invalid if user supplied more than one on command-line. Error for operation on single todo ID are reported as usual (for consistency with other commands sake and because I'm lazy and don't want to fix 2 tests :P).
-
- 27 Feb, 2015 1 commit
-
-
Bram Schoenmakers authored
Allow multiple tasks to be prioritized at once
-
- 26 Feb, 2015 1 commit
-
-
Jacek Sowiński authored
1. Shorter code for creating and populating 'todos' list 2. Merge IndexError and InvalidCommandArgument @bram85: Thanks!
-
- 10 Feb, 2015 1 commit
-
-
user authored
-
- 07 Feb, 2015 4 commits
-
-
Jacek Sowiński authored
-
Jacek Sowiński authored
Fixes issue #5
-
Bram Schoenmakers authored
When there is a todo in the list with an id: tag but no child todos, that value could be reused when creating a new dependency between two (unrelated) items. This is because the value of the dangling parent todo is not present in the dependency graph, but the function generating a new ID depended on that. Instead, simply iterate over all available todo items to check whether the proposed value already exists somewhere.
-
Bram Schoenmakers authored
When completing a command, show a warning when a 'rec' tag has an invalid recurrence pattern. Fixes issue #6. Conflicts: topydo/lib/DoCommand.py
-
- 06 Feb, 2015 1 commit
-
-
Bram Schoenmakers authored
-
- 04 Feb, 2015 10 commits
-
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
topydo may introduce some internal tags, such as 'id' and 'p' for dependency tracking, and 'ical' for keeping track of unique ids when outputting iCalendar files. Add a pretty printer filter that prevents certain tags from displaying in the 'ls' output. These tags can be configured with the 'hide_tags' configuration option in the 'ls' section, a comma-separated list of tags (default: id,p,ical). To always show all tags, leave an empty value.
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
Reset the configuration on tearDown, instead of at startup.
-
Bram Schoenmakers authored
This command is similar to the 'ls' subcommand, except that it prints the selected todo items as an iCalendar file. This can be read by other calendaring applications.
-
Bram Schoenmakers authored
The IcalCommand, which inherits from this class, wants to use the same view construction code, but needs a different implementation for printing the view. Therefore these two things should be split.
-
Bram Schoenmakers authored
There is no need for clients of printers to assume anything about the format. In this case, the View class assumed that the printer would return a list of strings, and then the view joined those entries. This latter step is actually the responsibility of the printer, so move it there.
-
- 24 Jan, 2015 1 commit
-
-
Bram Schoenmakers authored
Moreover, make print_todo of PrettyPrinter have the same signature as the Printer class. Clients must use add_filter to specify any additional filters when printing. The Command class holds a PrettyPrinter instance (rather than a generic printer). This means that add_filter is called, all future invocations of print_todo will apply these filters. This is not always desired, so in those cases a subcommand should instantiate its own printer (this happens for instance at the DoCommand).
-
- 23 Jan, 2015 3 commits
-
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
This allows for other printer implementations, where a printer is a transformation from a Todo item to a string.
-
Bram Schoenmakers authored
-