From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Lock CLOSED tag Date: Fri, 17 Jul 2009 16:27:15 +0200 Message-ID: <87eisfbd18.fsf@bzg.ath.cx> References: <200907101024.33972.aboudreault@mapgears.com> <87bpnk19ay.fsf@bzg.ath.cx> <200907170854.03027.aboudreault@mapgears.com> 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 1MRoPK-0003gF-8T for emacs-orgmode@gnu.org; Fri, 17 Jul 2009 10:27:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MRoPF-0003aQ-4l for emacs-orgmode@gnu.org; Fri, 17 Jul 2009 10:27:29 -0400 Received: from [199.232.76.173] (port=52320 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MRoPF-0003aN-0G for emacs-orgmode@gnu.org; Fri, 17 Jul 2009 10:27:25 -0400 Received: from ey-out-1920.google.com ([74.125.78.149]:45408) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MRoPE-0005xi-6b for emacs-orgmode@gnu.org; Fri, 17 Jul 2009 10:27:24 -0400 Received: by ey-out-1920.google.com with SMTP id 5so185861eyb.24 for ; Fri, 17 Jul 2009 07:27:22 -0700 (PDT) In-Reply-To: <200907170854.03027.aboudreault@mapgears.com> (Alan Boudreault's message of "Fri, 17 Jul 2009 08:54:02 -0400") 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: Alan Boudreault Cc: emacs-orgmode@gnu.org Hi Alan, Alan Boudreault writes: > I've take a look at the code you sugested to me. It didn't work. After further > documentation reading... it's definitively normal. "CLOSED" is not a todo tag > string... but a property (logdone). At this point, I have two choice: I assumed your original question was about locking a CLOSED todo keywords... > - If a similar hook exist for the property update when a tag has changed No. For now `org-blocker-hook' can only handle todo changes. > - Make a string list with all my "closed/done/fixed ... tags" and block those > changes. This way, I'll force a manual tag change when the current tag is a > closed one. I don't understand... can you give an example? > But, I would prefer the first idea because I normally switch my todo tag with > shift+(left|right)... so it pass through my 3 different todo sequences. What you mean by "todo tag" is a TODO keyword, right? "Tag" has as special meaning in Org. I think what you try to achieve can be better achieved wigth TODO keywords than with tags. Please do insist if I don't cleerly understand. -- Bastien