From: Bastien <bastienguerry@googlemail.com>
To: Alan Boudreault <aboudreault@mapgears.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Lock CLOSED tag
Date: Fri, 17 Jul 2009 16:27:15 +0200 [thread overview]
Message-ID: <87eisfbd18.fsf@bzg.ath.cx> (raw)
In-Reply-To: <200907170854.03027.aboudreault@mapgears.com> (Alan Boudreault's message of "Fri, 17 Jul 2009 08:54:02 -0400")
Hi Alan,
Alan Boudreault <aboudreault@mapgears.com> 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
next prev parent reply other threads:[~2009-07-17 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 14:24 Lock CLOSED tag Alan Boudreault
2009-07-10 17:36 ` Nicolas Goaziou
2009-07-10 18:00 ` Alan Boudreault
2009-07-16 23:45 ` Bastien
2009-07-17 12:54 ` Alan Boudreault
2009-07-17 14:27 ` Bastien [this message]
2009-07-17 15:16 ` Alan Boudreault
2009-07-17 15:29 ` Bastien
2009-07-17 15:39 ` Alan Boudreault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eisfbd18.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=aboudreault@mapgears.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).