From: "Dmitri Minaev" <minaev@gmail.com>
To: Renzo Been <swangdoodles@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Interpretation of priorities in org-mode
Date: Thu, 2 Aug 2007 11:07:18 +0500 [thread overview]
Message-ID: <b6c377310708012307r63e4245fo576085ad3a65fa39@mail.gmail.com> (raw)
In-Reply-To: <4916e1b50708010747n49b65809p7c94f7d8c804962f@mail.gmail.com>
On 8/1/07, Renzo Been <swangdoodles@gmail.com> wrote:
> But what is actually the difference between using:
> *priorities
>
> and:
> *Using tags
>
> You could make tags like this:
> Urgent
> Tomorow
> Low
Generally speaking, the priorities are a sorting tool. Tags may be
used for that goal, too, and by a sheer coincidence (or not?) the
proposed tags Urgent, Tomorrow and Low are in the right alphabetic
order. If you need more than 3 groups, however, you'll have to take
that into account. Also, it's OK to use tags instead of priorities as
long as you don't want the records to be sorted by yet another
criterion. Otherwise, you need something to complement the tags and
the priorities are perfect here.
Also, in the files where tags are used extensively, the tag you want
the records to be sorted by may happen to be in any position but the
last one, thus breaking the sorting.
That's why I prefer priorities to the corresponding tags, even though
the best use I have for them is setting the rating of the read books
:). They're simply indispensable for that goal.
--
With best regards,
Dmitri Minaev
Russian history blog: http://minaev.blogspot.com
prev parent reply other threads:[~2007-08-02 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 14:47 Interpretation of priorities in org-mode Renzo Been
2007-08-01 15:13 ` Piotr Zielinski
2007-08-01 16:52 ` Bastien
2007-08-09 5:05 ` Carsten Dominik
2007-08-02 6:07 ` Dmitri Minaev [this message]
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=b6c377310708012307r63e4245fo576085ad3a65fa39@mail.gmail.com \
--to=minaev@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=swangdoodles@gmail.com \
/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).