From: Bastien <bzg@altern.org>
To: Muchenxuan Tong <demon386@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature: Group and limit items in agenda
Date: Mon, 11 Feb 2013 14:42:13 +0100 [thread overview]
Message-ID: <87d2w6kier.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CANvjMg=j1CLHcykNSonPUqWf7VruHqmRyVNgkO7Tn-PCAmH55A@mail.gmail.com> (Muchenxuan Tong's message of "Mon, 11 Feb 2013 13:10:26 +0800")
Hi Muchenxuan,
Muchenxuan Tong <demon386@gmail.com> writes:
> My intention is to limit the number of tasks in each category.
Did you check (info "(org)Block Agenda") ?
That's the way I would suggest: define a block agenda listing
the various categories, then use `org-agenda-max-todos' in each
of them to limit the number of TODOs.
> For the new proposed 'org-agenda-max-todos', I can only limit the
> number of TODOs in the whole TODO lists.
>
> Maybe for what I want, it's desirable to add a auto-split or
> auto-group features, where a list of TODOs, can be split further into
> multiple lists of TODOs, by a certain criteria (tags, category).
>
> What do you think about it?
I understand defining block agendas is not as straightforward than the
solution you envision, but my feeling is that allowing grouping+limits
will have too much overlap with the block agenda functionality.
Let me know if you find the path to happiness with a combinaison of
block agendas and the new variables.
Thanks,
--
Bastien
next prev parent reply other threads:[~2013-02-11 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 18:13 Feature: Group and limit items in agenda Muchenxuan Tong
2013-01-23 21:35 ` AW
2013-02-07 10:41 ` Bastien
2013-02-11 5:10 ` Muchenxuan Tong
2013-02-11 13:42 ` Bastien [this message]
2013-02-17 6:29 ` Muchenxuan Tong
2013-02-23 9:58 ` Bastien
2013-02-24 20:23 ` Samuel Wales
2013-02-25 9:50 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2w6kier.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=demon386@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.