emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giorgio Valoti <giorgio_v@me.com>
To: emacs-orgmode@gnu.org
Subject: Re: Notes reviews with sparse trees
Date: Tue, 25 Jan 2011 17:09:51 +0100	[thread overview]
Message-ID: <98FD13EA-6404-4415-A08C-A5F96A519C79@me.com> (raw)
In-Reply-To: <AANLkTi=EaobJzBA3WmCoypS+XDMi4yE4GarT0NrS2T4G@mail.gmail.com>


Il giorno 25/gen/2011, alle ore 09.05, suvayu ali ha scritto:

> On Tue, Jan 25, 2011 at 7:00 AM, Giorgio Valoti <giorgio_v@me.com> wrote:
>> 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?
> 
> Well my suggestions is with using regexps, not what you asked. In any
> org buffer look at this variable:
> 
> 
> org-deadline-time-regexp is a variable defined in `org.el'.
> Its value is "\\<DEADLINE: *<\\([^>]+\\)>"
> Local in buffer notes.org; global value is nil
> 
>  Automatically becomes buffer-local when set in any fashion.
> 
> Documentation:
> Matches the DEADLINE keyword together with a time stamp.
> 
> 
> Now you could put your time stamps with a special tag, say "LAST:".
> You can choose to add it as keyword and fontify with the same face as
> DEADLINE, org-special-keyword-face. Then you can write your own defun
> using org-sparse-tree and a regex based on the above which uses the
> LAST: keyword to find the time stamps just like DEADLINEs. Does that
> work for you?

I didn’t think about using custom functions but it should work. 

Thank you a lot.


--
Giorgio Valoti

  reply	other threads:[~2011-01-25 16:10 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 [this message]
2011-01-27 18:32 ` Matt Lundin
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=98FD13EA-6404-4415-A08C-A5F96A519C79@me.com \
    --to=giorgio_v@me.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).