Comments (10)
3 years later, I am generally open to this idea and would support its implementation.
from taskwiki.
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
from taskwiki.
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.
from taskwiki.
backlog!
from taskwiki.
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
from taskwiki.
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.
from taskwiki.
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.
from taskwiki.
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) 🤔
from taskwiki.
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.
from taskwiki.
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
from taskwiki.
Related Issues (20)
- duplicate because tasks are recreated after sync HOT 2
- Tasklib regrusion, doesn't work in neovim 0.8 HOT 3
- Missing python dependencies. HOT 1
- Cannot add multiple tags when using viewports HOT 1
- Do viewports *need* a project to work? HOT 9
- Custom Priorities not supported
- Add / modify task in external editor
- handling of tasks with multiple parents needs improving HOT 1
- Hex color added to end of task line HOT 2
- Performance enchancement HOT 2
- have to reinstall to make it work
- Show filter query on viewports in normal mode when the cursor is on them HOT 3
- TaskCalendar colors not displaying (neovim v0.9.0)
- Is this project looking for new maintainers? HOT 2
- Use TaskWiki Anywhere HOT 2
- Customize Task UUID Symbol HOT 1
- Taskwiki breaks links' functionality on VimWiki index page HOT 1
- Stop recreate missing tasks
- Error message at startup HOT 2
- Update repository topics
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from taskwiki.