- 12 Jun, 2015 3 commits
-
-
Bram Schoenmakers authored
(Note that commenting/omitting archive_filename will still by default write the archived entries to done.txt). This addresses issue #42.
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
- 11 Jun, 2015 3 commits
-
-
Bram Schoenmakers authored
Conflicts: topydo/lib/DCommand.py
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
Expression-mode for del, depri, do, pri, postpone.
-
- 10 Jun, 2015 2 commits
-
-
Bram Schoenmakers authored
Fell into the trap of calling a function as a default parameter. Because of this, relative dates used with the 'add' or 'do' command (recurrence) were based on an offset when topydo was started, not when the subcommand was executed. Usually these two events occur in the same second and this bug was unnoticed for a long time. But now with prompt mode, this bug may surface if you leave running topydo for longer than a day.
-
Jacek Sowiński authored
- add test for direct todo.txt editing - remove unneceseary `u()`
-
- 09 Jun, 2015 3 commits
-
-
Jacek Sowiński authored
- execute_multi_specific() -> _execute_multi_specific() - execute_not_multi() -> _execute_not_multi()
-
Jacek Sowiński authored
MultiCommand._catch_todo_errors() prevents occuring of those.
-
Jacek Sowiński authored
-
- 08 Jun, 2015 4 commits
-
-
Jacek Sowiński authored
This required some refactoring in MultiCommand and ExpressionCommand. Whole part about processing flags was refactored. Code related to flags from DCommand was moved into MultiCommand and reused from there in all "multi" commands. New attribute: ExpressionCommand.last_argument. Should be set to True if command is using the last argument as something other than todo ID or part of an expression (as in case of postpone or pri). By default set to False. New method: MultiCommand.execute_not_multi(): wrapper for functionality not connected with todo IDs (like `topydo edit` or `topydo edit -d`). New attribute: MultiCommand.multi_mode: Should be set to True if user wants to operate on multiple todo items. True by default. New method: MultiCommand.get_todos_from_expr(): gets todo IDs based on expression and puts it in MultiCommand.todos. EditCommand._open_in_editor() now accepts only one argument - file to editing. It handles now also OSError exceptions. It is used also to opening todo.txt and done.txt. MultiCommand.get_todos() doesn't accept anymore todo IDs as an argument. Instead it's using inherited Expression.last_argument` to decide upon where to find todo IDs.
-
Jacek Sowiński authored
Now desired result of DCommand.get_flags() should be more apparent.
-
Jacek Sowiński authored
-
Jacek Sowiński authored
Now every call to editor is done by `EditCommand._open_in_editor()` and whole process of getting editor name is also done there.
-
- 07 Jun, 2015 1 commit
-
-
Bram Schoenmakers authored
When a subcommand finishes, _post_excecute() is called for sorting, archiving and writing the file. But sorting is also a subcommand, which in turn also calls _post_execute(), etc, etc. So let the caller of _execute() decide when to call _post_execute. This fixes issue #46.
-
- 06 Jun, 2015 12 commits
-
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
* Make TodoListTester test TodoListBase, make TodoListCleanDependencyTester test TodoList. This required moving a test case from the former class to the latter. * Add an additional test for a non-existent todo.
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
Just make sure that proper arguments are passed to GrepFilter in the first place.
-
Bram Schoenmakers authored
This started as a refactoring of the View class: to get rid of the pretty_print() function and anything releated to printers. So the View class now solely focusses on sorting and viewing a bunch of todos. It's up to the users of the View class to retrieve the todos in the view and pass them on to a Printer instance. The View class was quite involved with the proper Unicode support that was added lately. There were still encoded string passed through this class rather than Unicode strings. Getting rid of this affected basically all other places in the codebase. The result is that there are less string conversions; printed todo items stay Unicode as long as possible, until they're actually written out to standard output or to a file. I got rid of one text_type() call from the six library, all @python_2_unicode_compatible decorators are gone and the tests no longer need the utf8() function because everything is Unicode now. Remove utf8 function.
-
Bram Schoenmakers authored
-
- 04 Jun, 2015 3 commits
-
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
No need to toggle the highlighting of projects and contexts anymore. If you want to turn it off, simply assign an empty value to the project/context colors: [colorscheme] project_color = context_color =
-
Bram Schoenmakers authored
-
- 03 Jun, 2015 6 commits
-
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
-
Bram Schoenmakers authored
Thanks to Jacek for pointing out.
-
Bram Schoenmakers authored
Safe 16 base colors
-
- 02 Jun, 2015 3 commits
-
-
Jacek Sowiński authored
- Colors specified by name will return safe ANSI codes. - Colors specified by number will return ANSI code from xterm 256 color chart. - Defaults are also *safe*.
-
Bram Schoenmakers authored
This is a revert of commit fbed527f, which resulted in too many items after a project/context being highlighted. Instead, don't print a NEUTRAL_COLOR code at the end of the todo, but only when we finish applying all the color codes. This makes sure that the regexp to match a project/context also works at the end of a line. Also removed some logic to remove multiple sequences of NEUTRAL_COLOR at the end of the line, this is not necessary.
-
Jacek Sowiński authored
-