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

Buck Brody <buckbrody@gmail.com> wrote:

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

OK. Maybe the following will help. Define the following function
(perhaps in your .emacs):

(defun bb-mark-todays-deadlines-as-high-priority ()
"Find all entries with a DEADLINE of today and give them high priority."
  (interactive)
  (org-map-entries '(org-priority ?A) "+DEADLINE=\"<today>\"" 'file 'archive 'trees))

and invoke it in the project buffer with 

    M-x bb-mark-todays-deadlines-as-high-priority <RET>

(or bind it to some key for convenience). You might have to fiddle with
it a bit - the mapping API is described in section A.10 of the Org
manual.

HTH,
Nick

  reply	other threads:[~2010-04-28 22:34 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
2010-04-28 22:34             ` Nick Dokos [this message]
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=2102.1272494088@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=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).