emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: David Masterson <dsmasterson@outlook.com>
To: "joakim@verona.se" <joakim@verona.se>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Is is possible to summarize contents of a task in the agenda headings?
Date: Mon, 22 Apr 2019 06:20:14 +0000	[thread overview]
Message-ID: <SN6PR07MB574242D3B113B07B7A7A4E4BA5220@SN6PR07MB5742.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87tver9ran.fsf@chopper> (joakim's message of "Sun, 21 Apr 2019 19:55:28 +0200")

<joakim@verona.se> writes:

> Say I have a bunch of tasks like this:
>
> * TODO task with many subtasks
> ** TODO subtask 1
> ** TODO subtask 2
> * TODO another task with many subtasks
> ** TODO another subtask 1
> ** TODO another subtask 2
>
> And so on.
>
> Now, in the agenda, I would like some kind of summarizing, perhaps like:
>
> * TODO task with many subtasks, subtask 1, subtask 2
> * TODO another task with many subtasks, another subtask 1, another subtask 2
>
> Is this possible?
>
> The reason is that I have many "tasks with many subtasks", so I have
> used the setting to hide them in the Agenda. Still, I would like to know
> something about the contents of such grouping tasks in the agenda, if
> possible.

Maybe you want the 'org-agenda-todo-list-sublevels' variable?

Another more complicated option that I've just begun looking at is the
:agenda-group capability in the org-super-agenda package on MELPA.  The
documentation is interesting on the website, but I haven't quite figured
out the trick to make it work for me.  You can find it here:

https://github.com/alphapapa/org-super-agenda

--
David Masterson

next prev parent reply	other threads:[~2019-04-22  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21 17:55 Is is possible to summarize contents of a task in the agenda headings? joakim
2019-04-22  6:20 ` David Masterson [this message]
2019-04-23 19:35   ` joakim
2019-04-26  3:39     ` David Masterson
2019-05-06  8:09       ` joakim
2019-05-08 23:46         ` Adrian Bradd

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=SN6PR07MB574242D3B113B07B7A7A4E4BA5220@SN6PR07MB5742.namprd07.prod.outlook.com \
    --to=dsmasterson@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=joakim@verona.se \
    /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

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