gtg_new_task does not support subtasks
Bug #591130 reported by
Luca Invernizzi
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GTG |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
[from a question of Pablo Olmos de Aguilera Corradini]
just found the gtg_new_task file and works quite well, the thing is that when I launch it in interactive mode like:
$ gtg_new_task -i "title"
@tag
body
trying to add subtasks
- subtask
- subtask 2
-- subsubtask
It parse it fine except for the subtask thing that only appears as a hyphen and not the arrow that indicates to gtg that it is a subtask (a ss for you to understand).
| description: | updated |
Revision history for this message
| Lionel Dricot (ploum-deactivatedaccount) wrote | #1 |
| Changed in gtg: | |
| importance: | Undecided → Wishlist |
| Changed in gtg: | |
| status: | New → Confirmed |
| milestone: | none → 0.4 |
| tags: | added: editor |
| Changed in gtg: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
The parsing of the tasks is done at the Editor level when you type.
The reason is because you don't want to change the content of a text that it's saved.
I see two possible way :
1) make the gtg_new_task parse the content.
2) give gtg_new_task some option to add subtasks.
I would choose option 2) as we don't know what can be the input. Imagine a script that creates new tasks based on email, it would create subtasks for items in the discussion.