{"action":"created","issue":{"url":"https://api.github.com/repos/blakesweeney/unite-taskwarrior/issues/36","labels_url":"https://api.github.com/repos/blakesweeney/unite-taskwarrior/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/blakesweeney/unite-taskwarrior/issues/36/comments","events_url":"https://api.github.com/repos/blakesweeney/unite-taskwarrior/issues/36/events","html_url":"https://github.com/blakesweeney/unite-taskwarrior/issues/36","id":104101276,"number":36,"title":"taskwiki integration","user":{"login":"linuxcaffe","id":2353531,"avatar_url":"https://avatars.githubusercontent.com/u/2353531?v=3","gravatar_id":"","url":"https://api.github.com/users/linuxcaffe","html_url":"https://github.com/linuxcaffe","followers_url":"https://api.github.com/users/linuxcaffe/followers","following_url":"https://api.github.com/users/linuxcaffe/following{/other_user}","gists_url":"https://api.github.com/users/linuxcaffe/gists{/gist_id}","starred_url":"https://api.github.com/users/linuxcaffe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/linuxcaffe/subscriptions","organizations_url":"https://api.github.com/users/linuxcaffe/orgs","repos_url":"https://api.github.com/users/linuxcaffe/repos","events_url":"https://api.github.com/users/linuxcaffe/events{/privacy}","received_events_url":"https://api.github.com/users/linuxcaffe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-31T17:57:58Z","updated_at":"2015-09-01T14:06:50Z","closed_at":null,"body":"unite-taskwarrior shares the vim/taskwarrior space with two other established projects; taskwiki and vim-taskwarrior, and a user who installs one might install more than one. This \"issue\" is to discuss ways to make that more seamless and advantageous with taskwiki. (more on vim-taskwarrior elsewhere)\r\n\r\nsome of these behaviors only make sense if the other projects are installed, so using those features could be made optional with a config;\r\n<pre>\r\ng:unite_taskwarrior_use_taskwiki=1\r\ng:unite_taskwarrior_use_vim-taskwarrior=1\r\n</pre>\r\n1. taskwiki format\r\n    taskwiki displays tasks in a format based on vimwiki tasks. If Utw can (optionally) render tasks in this format, any tasks printed to a file will become \"live\" entries, maintained by taskwiki. Also, tasks in this format can be highlighted using taskwiki and vimwiki syntax. I'm not suggesting that utw would then _always_ use taskwiki format, just where advantageous. That format looks like:\r\n\r\n<pre>\r\n    * [ ] Do this important task(DUE DATE)  #UUID_SHORT\r\n</pre>\r\nas well, utw/taskwiki use the \"[ ]\" symbol differently, utw with [-] [+] and taskwiki with [X] [D] [S] so some \"harmonization\" need to take place between the two projects, so all of this info can be displayed in either one. (I have ideas ;-)\r\n2. wiki action; when a task is selected, a new action is available \"wiki\" which opens the appropriate wiki-file, based on a simple formula.\r\n3. On creation of a tasknote, as in the bottom of #10 , inserting a taskwiki-formatted task, as first line of the tasknote, would super-charge it. \r\n\r\nThere are probably other things that I think would make utw taskwiki-compatible, but I can't think of any :)\r\n\r\n\r\n\r\n  "},"comment":{"url":"https://api.github.com/repos/blakesweeney/unite-taskwarrior/issues/comments/136733436","html_url":"https://github.com/blakesweeney/unite-taskwarrior/issues/36#issuecomment-136733436","issue_url":"https://api.github.com/repos/blakesweeney/unite-taskwarrior/issues/36","id":136733436,"user":{"login":"linuxcaffe","id":2353531,"avatar_url":"https://avatars.githubusercontent.com/u/2353531?v=3","gravatar_id":"","url":"https://api.github.com/users/linuxcaffe","html_url":"https://github.com/linuxcaffe","followers_url":"https://api.github.com/users/linuxcaffe/followers","following_url":"https://api.github.com/users/linuxcaffe/following{/other_user}","gists_url":"https://api.github.com/users/linuxcaffe/gists{/gist_id}","starred_url":"https://api.github.com/users/linuxcaffe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/linuxcaffe/subscriptions","organizations_url":"https://api.github.com/users/linuxcaffe/orgs","repos_url":"https://api.github.com/users/linuxcaffe/repos","events_url":"https://api.github.com/users/linuxcaffe/events{/privacy}","received_events_url":"https://api.github.com/users/linuxcaffe/received_events","type":"User","site_admin":false},"created_at":"2015-09-01T14:06:50Z","updated_at":"2015-09-01T14:06:50Z","body":"Very cool Blake, I think we're on the same page.\r\n\r\n  1. I like that Unite and taskwiki can have different display formatting, Utw will probably be the more configurable of the two, The only place(s) I would want Utw to use the taskwiki format is when tasks are read into a buffer, like the top line of a tasknote, or to populate a taskwiki page.\r\n\r\n   2. Opening the appropriate wiki page (in my world, which I hope to share) is;\r\n\r\n1. if a task has a wiki-back-link (an annotation with \"wiki: path/to/file.wiki\", a feature of taskwiki) then go to that, else,\r\n2. if a task has a project, go to $WIKIDIR/project/project-name.project.wiki, else\r\n3, if a task has no backlink or project, open $WIKIDIR/index.wiki\r\n\r\n  3. I agree\r\n\r\n"}}