From: Matthew Lundin <mdl@imapmail.org>
To: buckbrody@gmail.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: due today notification
Date: Wed, 28 Apr 2010 15:57:27 -0400 [thread overview]
Message-ID: <87eihzwdso.fsf@fastmail.fm> (raw)
In-Reply-To: <w2h8bd4668a1004281212yb454795dn600be1995711db85@mail.gmail.com> (Buck Brody's message of "Wed, 28 Apr 2010 15:12:03 -0400")
Buck Brody <buckbrody@gmail.com> writes:
> > Might I ask why the sparse tree search above or a simple agenda
> > view of deadlines is inadequate? The daily agenda provides a nice
> > view of all deadlines, making clear which are due today and which
> > are past due. And with a custom agenda command you can see only
> > those items that are due today:
>
> 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.
>
But isn't this precisely what a sparse tree does? I.e., it highlights
the relevant deadlines but preserves the context...
I dug around in the source code and found a command (normally invoked by
org-sparse-tree) that shows all deadlines in a file within n days
(determined by a prefix argument).
If you type...
C-u 1 M-x org-check-deadlines
...org-mode will highlight all the deadlines in the buffer due today or
past due. You could bind this to a key.
Best,
Matt
next prev parent reply other threads:[~2010-04-28 19:49 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 [this message]
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
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=87eihzwdso.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=buckbrody@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 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).