emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Giorgio Valoti <giorgio_v@me.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Notes reviews with sparse trees
Date: Thu, 27 Jan 2011 13:32:28 -0500	[thread overview]
Message-ID: <87ei7yqjsz.fsf@fastmail.fm> (raw)
In-Reply-To: <11D6DC00-9527-41AC-9067-F0D126322AF3@me.com> (Giorgio Valoti's message of "Tue, 25 Jan 2011 07:00:48 +0100")

Giorgio Valoti <giorgio_v@me.com> writes:

> since I started using Org I collected a bunch of notes in a journal
> file and I’d like to review them on a regular schedule. Ideally, I’d
> like to mark a given entry with a review timestamp so I can skip it
> the next I review the journal file and then use a sparse tree to see
> only the notes that I haven’t reviewed in a while.
>
> The problem is that I can’t get a sparse tree using these timestamps
> because it works only with deadlines and schedules. Does anybody know
> how to work around this limitation, short of using a regexp?

You can use tags/property matches for this.

For all inactive timestamps more than two weeks in the past:

C-c / m TIMESTAMP_IA<"<-2w>"

The same for all active timestamps:

C-c / m TIMESTAMP<"<-2w>"

For inactive timestamps, more than one week old and less than two weeks
old:

C-c / m TIMESTAMP_IA<"<-1w>"+TIMESTAMP_IA>"<-2w>"

For today's timestamps:

C-c / m TIMESTAMP="<today>"

And so on...

Please see the following for more details:

(info "(org) Matching tags and properties")
(info "(org) Special properties")

http://orgmode.org/worg/org-tutorials/advanced-searching.html#special-properties

Best,
Matt

  parent reply	other threads:[~2011-01-27 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  6:00 Notes reviews with sparse trees Giorgio Valoti
2011-01-25  8:05 ` suvayu ali
2011-01-25 16:09   ` Giorgio Valoti
2011-01-27 18:32 ` Matt Lundin [this message]
2011-01-28  5:31   ` Giorgio Valoti

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=87ei7yqjsz.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=giorgio_v@me.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).