emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Buck Brody <buckbrody@gmail.com>
To: "nicholas.dokos" <nicholas.dokos@hp.com>
Cc: Matthew Lundin <mdl@imapmail.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: due today notification
Date: Wed, 28 Apr 2010 17:29:45 -0400	[thread overview]
Message-ID: <y2t8bd4668a1004281429x361a5b3fg9c2f45e8510b75@mail.gmail.com> (raw)
In-Reply-To: <30668.1272487604@alphaville.usa.hp.com>


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

Nick,

Thanks for the suggestion.

What I want is a way to know, just by looking at a headline, if it is due
today.  Maybe this isn't something most people care about because they keep
their files unfolded most of the time, so they can see the DEADLINE
property.  All my tasks are kept on the third level and I don't usually keep
the file unfolded past that because I wouldn't be able to see enough
headlines at once.

Maybe it would be best if I explain my current workflow.  I use agenda to
see what is due today.  I then manually assign those items the A priority.
 For the rest of the day, whether I am in a different agenda view, or just
within my main file, I can quickly see what items are due today because they
have the A priority within the headline.  Using a tag would work just as
well.  I am looking for a way to cut out this manual process.

I appreciate everyone's help, but I don't want to use up a lot of peoples
time because this is not that big a problem for me.

Thanks,

Buck

On Wed, Apr 28, 2010 at 4:46 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> Buck Brody <buckbrody@gmail.com> wrote:
>
>
> > Assume I have 10 things that must be done for a specific project and two
> of
> > them must be done today.  I want to be able to know which two are due
> today,
> > but I still want to see them in the same list as the other 8 items
> because
> > it gives useful context.
> >
>
> Coming late to the party and I'm almost sure that the following will not
> satisfy you, but maybe it'll help the rest of us understand what you are
> really after (afaict, that's still not clear - apologies if I'm
> generalizing unwarrantedly).
>
> Say you have project foo with project file foo.org:
>
> ,----
> | #+STARTUP: showall
> | *** Long list of project items
> | **** a
> | **** b
> | **** c
> |      DEADLINE: <2010-04-28 Wed>
> | **** d
> | **** e
> | **** f
> |
> | **** g
> |
> | **** h
> |      DEADLINE: <2010-04-28 Wed>
> | **** i
> | **** j
> `----
>
> Items c and h are due today. I assume you have added the file to your
> agenda list.  Then you look at your agenda and you get:
>
> ,----
> | Week-agenda (W17-W18):
> | Wednesday  28 April 2010
> |   ...
> |   foo:        Deadline:   c
> |   foo:        Deadline:   h
> |   ...
> | Thursday   29 April 2010
> |   ...
> `----
>
> Click on the c line and press <RET>: you are in foo.org, on item c,
> and there's your context. Ditto for the h line in the agenda.
>
> If this does not satisfy you, what would you like to have seen instead?
>
> HTH in some small way,
> Nick
>
>

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

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

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-04-28 21:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 17:12 due today notification Buck Brody
2010-04-23 22:54 ` Matt Lundin
2010-04-26 16:48   ` Buck Brody
2010-04-27 19:01     ` Matthew Lundin
2010-04-28 19:12       ` Buck Brody
2010-04-28 19:57         ` Matthew Lundin
2010-04-28 20:14           ` Buck Brody
2010-04-28 20:38             ` Matthew Lundin
2010-04-28 20:46         ` Nick Dokos
2010-04-28 21:29           ` Buck Brody [this message]
2010-04-28 22:34             ` Nick Dokos
2010-04-24  7:40 ` 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

  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=y2t8bd4668a1004281429x361a5b3fg9c2f45e8510b75@mail.gmail.com \
    --to=buckbrody@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --cc=nicholas.dokos@hp.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).