emacs/var/elfeed/db/data/f1/f11548c616c5531089751d9b85bf14f0eca9a5ba
2022-01-03 12:49:32 -06:00

1 line
1.5 KiB
Plaintext

<!-- SC_OFF --><div class="md"><p>The documents mode are a tree based data structure. A graph based data structure is more powerful to express task dependency. Even we use some plugin like org-edna/org-depend to express a dependant task of a headline h1 who isn&#39;t a descendant of h1, all functions on subtask can run only for descendant of a headline.</p> <p>For instance, what will happen if 2 projects p1 and p2 depend a same task t1. t1 is a descendant of p1. And we want know the progress of p2, the progress of t1 won&#39;t be integrated to calculation of progress of p2.</p> <p>To solve this problem, org mode should integrate the notion of symbolic link headline, like in tree based file system, we have file and symlink into a file. I don&#39;t think org mode will evolve into this direction, because it is designed to write documents. A document don&#39;t need this feature.</p> <p>What do you think about this limit of org mode to become the ideal task management? How you bypass the problem?</p> <p>I think to switch into a graph based task management system. Someone know a good open source graph based task management system? If possible like emacs, is fully customizable.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/terhyrzht"> /u/terhyrzht </a> <br/> <span><a href="https://www.reddit.com/r/orgmode/comments/qyrtdn/the_limit_of_org_mode_to_become_the_ideal_task/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/orgmode/comments/qyrtdn/the_limit_of_org_mode_to_become_the_ideal_task/">[comments]</a></span>