From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Adams Subject: Re: depending TODOs, scheduling following TODOs automatically Date: Thu, 11 Oct 2007 08:21:48 -0500 Message-ID: <20071011132148.GB6275@odin.demosthenes.org> References: <877ilxmimn.fsf@bzg.ath.cx> <877ilxnh44.fsf@bzg.ath.cx> <87wstwk1sz.fsf@bzg.ath.cx> <874pgxizxg.fsf@bzg.ath.cx> <20071011122234.GA6275@odin.demosthenes.org> <87odf5hhp5.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ifxz8-0002hO-Dr for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 09:21:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ifxz7-0002fN-33 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 09:21:53 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ifxz6-0002f0-UO for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 09:21:52 -0400 Received: from squirtle.drak.net ([72.52.144.201]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ifxz6-0001KG-H0 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 09:21:52 -0400 Received: from 206.180.154.177.adsl.hal-pc.org ([206.180.154.177] helo=localhost) by squirtle.drak.net with esmtpa (Exim 4.68) (envelope-from ) id 1Ifxz0-0001vV-H9 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 08:21:46 -0500 Content-Disposition: inline In-Reply-To: <87odf5hhp5.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org > I a sense, that shows that having a proper GUID system will only be > useful in case there are many tasks with the same name, which should > already be discouraged since headlines may show up in the agenda buffer > with no context at all. I rarely have issues with conflicts in agenda. I use discreet files for separate projects, and unique subitems are scheduled. Otherwise I'll deal with duplicates. ;] > > IMO, a better rationale behind GUID is that headlines can change and > thus not be reached anymore by a search string. Having a GUID would > fix this. But I'm definitely not a GUID-fan, sorry :) I'm not a fan either, but recognize that it is a fast fix. You can use a static property and simplified search (vs regexp) and know that you've matched the correct item. That being said, perhaps the GUID should be dynamic and similar to the links interface. By default, no items have properties, or GUID's. If you trigger a "save location", a GUID is added to the current item adding a property drawer as needed. You can then choose that TODO from a list when creating the dependency (again, just like links). Thats what came to mind for me. ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3