emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Daniel Goldin" <danielgoldin@gmail.com>
To: Manish <mailtomanish.sharma@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: see subtrees in agenda
Date: Tue, 22 Apr 2008 08:18:57 -0700	[thread overview]
Message-ID: <d1c140d50804220818l3453bedeteca34b5c2af1480d@mail.gmail.com> (raw)
In-Reply-To: <e7cdbe30804212327m10451e52ta77e6d1f7c026d53@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1721 bytes --]

Dear Manish,

Not quite. Although these are very useful enhancements while I'm at the
computer, I was looking for something that I could publish -- so I could
carry around a hard copy showing contextual levels.

For example

* Let Jimmy know about annual picnic
** NEXT Write letter to Jimmy                               @COMPUTER
** NEXT Send it                                                    @ERRAND

If when I look for all todo items matching NEXT, I'll see:

** Write letter
** Send it

Which when I publish doesn't tell me enough. Of course I could become more
verbose in my sub-level captions, but it would be better to see relevant
headlines and relevant sub-headlines.

d.

On Mon, Apr 21, 2008 at 11:27 PM, Manish <mailtomanish.sharma@gmail.com>
wrote:

>  Carsten> > On Mon, Apr 21, 2008 at 2:11 AM, Carsten Dominik wrote:
>  Carsten> > > Can you please be more specific with your request?
>  Carsten> > >  An example, maybe?
>
>  Jeff> > I think he means something like the following:
>  Jeff> >
>  Jeff> > ** TODO This amazing event
>  Jeff> >     DEADLINE: <2008-04-21 Mon>
>  Jeff> > *** TODO First part of the event
>  Jeff> > *** TODO Second part of the event
>  Jeff> >
>  Jeff> > And then in agenda instead of seeing just:
>  Jeff> > This amazing event
>  Jeff> >
>  Jeff> > You'd see the subtree as well:
>  Jeff> > This amazing event
>  Jeff> >    First part of the event
>  Jeff> >    Second part of the event
>
>  Daniel> > That is exactly what I meant. Thanks for the example and
> the translation.
>
>  Please check out `f' (org-agenda-follow-mode) and `b'
> (org-agenda-tree-to-indirect-buffer) in agenda view.  May be they
> would suffice?
>
> -- Manish
>



-- 
Daniel Goldin
626-795-9526

[-- Attachment #1.2: Type: text/html, Size: 2829 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
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:[~2008-04-22 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 21:42 see subtrees in agenda Daniel Goldin
2008-04-21  6:11 ` Carsten Dominik
2008-04-21  6:27   ` Jeff Mickey
2008-04-21 18:12     ` Daniel Goldin
2008-04-22  6:27       ` Manish
2008-04-22 15:18         ` Daniel Goldin [this message]
2008-04-22 16:46           ` Manish
2008-04-23 15:07             ` Daniel Goldin

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=d1c140d50804220818l3453bedeteca34b5c2af1480d@mail.gmail.com \
    --to=danielgoldin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mailtomanish.sharma@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).