emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: outline-agenda sorting consistency
Date: Thu, 19 Feb 2009 20:22:32 +0100	[thread overview]
Message-ID: <12A93522-C936-4A08-AE29-3CE19A6B29CB@uva.nl> (raw)
In-Reply-To: <20524da70902102136m43cc7206q88d9f992cd280bfe@mail.gmail.com>

Hi Samuel,
On Feb 11, 2009, at 6:36 AM, Samuel Wales wrote:

> Here are some possible ways that the outline and the agenda
> could be made slightly more consistent.  Hope I didn't miss
> any that already exist.
> 1) priority faces are settable in the agenda.  perhaps
>    they could be so in the outline also.

This seems more confusing than useful to me.  In the agenda,
all the tasks are together, so it does make some sense to
change fonts.  In the outline, I would find it confusing.
Are there any other opinions on this?

> 2) sorting strategy is settable in the agenda.  perhaps it
>    could be settable in the outline also.  they could
>    share code.

To be honest, I never sort the outline, except in rare cases.
I would be interested how people use this to get a better case
for changing this.

One of the basic principles in Org is that in the notes files,
tasks are in context.  In the agenda, things are re-arranged
and sorted.  That is why there is a complex sorting strategy
in the agenda, but not in the outline.

- Carsten

>    also:
>    * priorities are sortable.  perhaps tags can be
>      sortable via a default (built-in) sorting strategy
>      also.
>      to set the weights, the user configures as follows.
>      nil means that tag sorting does nothing.
>      ;;urgent gets sorted highest (or lowest, depending on
>      ;;perspective).  this is very useful for people who
>      ;;have some ordered tags.
>      (setq org-tag-sort-weights
>            '(("urgent" . 1000)
>              ("now" . 100)
>              ;;below no tag
>              ("someday" . -100))
>              ;;nutrition is more important than entertainment
>              ("nutrition" . 100)
>              ("entertainment" . -100))
>    * todo states are sortable.  perhaps they can be
>      sortable in such a way that the user can put blank
>      entries (no todo state) as desired (e.g. between TODO
>      and DONE).  perhaps a variable to set the weights.
> -- 
> Myalgic encephalomyelitis denialists are causing massive suffering and
> 25-years-early death by grossly corrupting science.
> http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-02-19 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  5:36 outline-agenda sorting consistency Samuel Wales
2009-02-19 19:22 ` Carsten Dominik [this message]
2009-03-03  4:09   ` Samuel Wales
2009-03-04 11:53     ` Carsten Dominik
2009-03-14  3:18       ` Samuel Wales

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:

  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=12A93522-C936-4A08-AE29-3CE19A6B29CB@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \


* 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


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).