John Hendy <jw.he...@gmail.com> writes: > I agree and would prefer this. Especially since folks wanting to > export and being allowed to access tj functionality through drawers > are probably going to anticipate using actual tj syntax in those > drawers. Since tj only forces unique global ids (one can have M.T8, > T.T8, etc.), this would solve the issue of ambiguity should one decide > to use non-globally unique task ids. In fact, many projects may very > well use a lot of repetitive tasks with the same properties. > > In mine, I have some tasks regarding shipping products to various > countries. This way I could just have a bunch of country-specific > headlines like: > > * Country > ** Ship product > > * Country 2 > ** Ship product > > And could give all the ** Ship... tasks the same id since their > Country parent would make it globally unique.
You can already do so. IDs only have to be unique within the task siblings. > For now, I'm just happy to have functionality restored so I can use > Org and not hand-edit the files after exporting :) I have a potential > IRC date with Christian Egli sometime this week... perhaps you should > join and add your feedback? One of my other points of input would be > that something like C-c l (Org store link at point) would be great. > Unique ids could be inserted as depends with some simple key strokes > and I would't have to use numbered IDs at all. They'd stay with the > tasks no matter where I moved them. > > For that... I'd actually prefer *not* to have to explicitly name the > parent since they could move wherever I put them with no consequence. You don't have to name parents either. You only need to name tasks that will be used as a dependency. Regards, -- Nicolas Goaziou
