Open linuxcaffe opened 9 years ago
I'm not sure I would want to implement this.
Currently we have a easy mapping: 1 task = 1 line. This allows for easy parsing, generation / deletion of tasks in viewports.
This would also have to be configurable, as I can imagine users with heavy annotation usage would want to hide this list.
In general, anything that changes the number of lines per task is going to be hard to implement unless this concept is generalized.
backlog!
Is it nearly time for this one? what with dependency indentation as a model, and task 2.5.x handling of \n multi-line annotations..
Being able to freely see/ add annotations as indented list-items under any given task, would be really really good, you know it would!
.. just a nudge
3 years later, I am generally open to this idea and would support its implementation.
I would also really appreciate this functionality. Do you have any estimate of how much work it would be to implement? If it is a matter of an afternoon, I would consider having a go just in order to better understand this extremely impressive plugin.
I'm assuming the violation of 1 task = 1 line will introduce some complexities. Will it be simpler if we can implement this as a tooltip? perhaps using something like https://github.com/yshui/tooltip.nvim ? Not aware of a solution for regular Vim though.
Tooltips would definitely work, and I guess I would be fine with that bonus functionality working only in neovim
.
I'm assuming however, that in order for the tooltip to show, you need to hover over that line anyway - in which case, it wouldn't be that much different from hitting Enter to display the output of task info
(:TaskWikiInfo
command) :thinking:
Agreed, also realized it would be read only which will work for my use case but not if someone wants to add the annotations easily as OP pointed out.
How would this work with child tasks? If I have a task that has both annotations and child tasks, will they look like this:
* [ ] Task1
* Task1 annotation1
* [ ] Child-task1
* Child-task1 annotation1
* [ ] Child-task2
* Task1 annotation2
* [ ] Child-task3
There should be ways to work around that. For example, the annotations could be displayed first, followed by the child tasks:
* [ ] Task1
* Task1 annotation1
* Task1 annotation2
* [ ] Child-task1
* Child-task1 annotation1
* [ ] Child-task2
* [ ] Child-task3
Annotations can be logically presented/ created as indented list items, under a task. As long as the text-block remains contiguous, then annotations should not affect dependency/ hierarchy,