RE: [Orgmode] Interpretation of priorities in org-mode

2007-08-02 Thread Egli Christian (KIRO 41)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Piotr Zielinski Sent: Wednesday, August 01, 2007 5:24 PM To: Jason F. McBrayer Cc: emacs-orgmode@gnu.org Subject: Re: [Orgmode] Interpretation of priorities in org-mode If something has to be done today

Re: [Orgmode] Interpretation of priorities in org-mode

2007-08-01 Thread Jason F. McBrayer
Piotr Zielinski [EMAIL PROTECTED] writes: I'd like to find out how different people use priorities (#A, #B, ...) in org-mode. I've always assumed the standard interpretation (#A = high priority, #B = medium, #C = low). However, the problem with this approach is that what high priority means

Re: [Orgmode] Interpretation of priorities in org-mode

2007-08-01 Thread Piotr Zielinski
On 01/08/07, Jason F. McBrayer [EMAIL PROTECTED] wrote: I don't really use priorities at all, since I'm using org-mode to do GTD. I agree with you on that, I was only suggesting using priorities as a technical means to label certain tasks as to do today in a way which is easy in org-mode. If

Re: [Orgmode] Interpretation of priorities in org-mode

2007-07-31 Thread Bastien
Hi Piotr, Piotr Zielinski [EMAIL PROTECTED] writes: I've been recently experimenting with a different interpretation of priorities: #B = tasks to do today, #C = tasks to do this week, #D = all the rest, default. #A is reserved at the moment. One good thing about this system is a clearer