emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tim O'Callaghan" <tim.ocallaghan@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Agenda Focus Mode - An Agenda Idea.
Date: Wed, 5 Sep 2007 16:27:28 +0200	[thread overview]
Message-ID: <3d6808890709050727x66f54209mbd18e6b5bb806035@mail.gmail.com> (raw)
In-Reply-To: <01809536df836a7c68577b69f6ac1356@science.uva.nl>

On 05/09/07, Carsten Dominik <dominik@science.uva.nl> wrote:
> On Sep 5, 2007, at 15:23, Tim O'Callaghan wrote:
> > On 05/09/07, Carsten Dominik <dominik@science.uva.nl> wrote:
> >> Do you mean for interactive use, to be able to specify the regexp at
> >> the prompt?
> >> Or in an org-agenda-custom-command?
> >>
> >
> > I meant an org-agenda-custom-command,
> Check Appendix A5, near the end if it, there are examples on how to use
> `org-agenda-skip-function', and it includes the option to
> select on or against a regular expression.  You need something like
> (org-agenda-skip-function
>   '(org-agenda-skip-entry-if 'notregexp "^\\*+\\<Resolve\\>))
> Note that I have anchored the regexp at the beginning of the headline
> with
> "^\\*+", to make sure that it only matches in the headline and not
> somewhere
> in the tree.
Thanks, I shall play with this.

For the record, i did look at Appendix5, but notregexp was not
mentioned. Could you add it to the A5 Examples?

This is a close approximation to what i want to do, and should be
useful for focusing next actions. Checking Projects would require tag
inheritance i think.

> >  but it might be useful at the
> > command prompt.
> This is currently not possible.



  reply	other threads:[~2007-09-05 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  9:46 Agenda Focus Mode - An Agenda Idea Tim O'Callaghan
2007-09-05 13:08 ` Carsten Dominik
2007-09-05 13:23   ` Tim O'Callaghan
2007-09-05 13:39     ` Carsten Dominik
2007-09-05 14:27       ` Tim O'Callaghan [this message]
2007-09-05 15:43         ` Carsten Dominik

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:

  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=3d6808890709050727x66f54209mbd18e6b5bb806035@mail.gmail.com \
    --to=tim.ocallaghan@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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