From: Buck Brody <buckbrody@gmail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: due today notification
Date: Wed, 28 Apr 2010 15:12:03 -0400 [thread overview]
Message-ID: <w2h8bd4668a1004281212yb454795dn600be1995711db85@mail.gmail.com> (raw)
In-Reply-To: <87wrvs7m9q.fsf@fastmail.fm>
[-- Attachment #1.1: Type: text/plain, Size: 1807 bytes --]
Matt,
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.
Buck
On Tue, Apr 27, 2010 at 3:01 PM, Matthew Lundin <mdl@imapmail.org> wrote:
> Hi Buck,
>
> Buck Brody <buckbrody@gmail.com> writes:
>
> > Sorry, I don't think I properly described what I am looking for. I
> > want a visual indicator (like a tag or a face) of tasks due today, but
> > I don't want to do a specific search. The idea would be that, within a
> > view of all tasks, I would be able to see at a glance which were due
> > today. Does that make sense?
>
> I'm not aware of any such functionality. One solution, I suppose, would
> be to use org-map-entries and a custom function to add a tag to all
> entries due today. But adding the tags with org-map-entries would likely
> be just as slow as a search, so there may not be much point.
>
> (info "(org) Using the mapping API")
>
> > On Fri, Apr 23, 2010 at 6:54 PM, Matt Lundin <mdl@imapmail.org> wrote:
> >
> > C-c / m DEADLINE="<today>" [RET]
> >
>
> 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:
>
> --8<---------------cut here---------------start------------->8---
> (setq org-agenda-custom-commands
> '(("d" "Due today" agenda ""
> ((org-agenda-entry-types '(:deadline))
> (org-deadline-warning-days 0)))))
> --8<---------------cut here---------------end--------------->8---
>
> Best,
> Matt
>
[-- Attachment #1.2: Type: text/html, Size: 2533 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
next prev parent reply other threads:[~2010-04-28 19:12 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 [this message]
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
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=w2h8bd4668a1004281212yb454795dn600be1995711db85@mail.gmail.com \
--to=buckbrody@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).