emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@uva.nl>
To: pholcomb@cpoint.net
Cc: emacs-orgmode@gnu.org
Subject: Re: Help with agenda-custom commands
Date: Sun, 28 Sep 2008 07:16:41 +0200	[thread overview]
Message-ID: <F7DA25EC-0D9E-474D-B7C0-9325590010F5@uva.nl> (raw)
In-Reply-To: <20080924231637.GM28285@cpoint.net>


[-- Attachment #1.1: Type: text/plain, Size: 1778 bytes --]

Hi Paul,


On Sep 25, 2008, at 1:16 AM, Paul Holcomb wrote:

>
> I'm pretty new to elisp and I'm having difficulty figuring out how
> to implement two things in org-agenda-custom-commands:
>
> *) Is there a simple way to construct an agenda view that:
>  -shows all past scheduled events for one TODO keyword only
>  -skips for all others
>
> The only way I could figure out it could work is to write a large
> org-agenda-skip function that explicitly looks at subtrees and
> duplicates the org-scheduled-past-days check code.
>
> Unless I'm mistaken a block view won't work because the value of
> org-scheduled-past-days is local to the agenda command and not each
> block inside of it.

I have not tested this, but you might be able to use the general tags/ 
property/todo matcher
on `C-c a m' like this:

SCHEDULED<"<today>"/!+MYTODOKEYWORD

> *) Using a defconst symbol or function that evaluates to a stringp
> in place of an actual string in for the match field.
>
> ex:
>      ("A" ""  tags-todo 'org-pah-todo-exclude nil nil)
>
>
>           (type-of org-pah-todo-exclude)
> 	        ==> stringp
>
>  I also tried using concat and format for that argument.  The error
>  is always:
>
>  Debugger entered--Lisp error: (wrong-type-argument stringp (quote  
> org-pah-todo-exclude))
>    string-match("/+" (quote org-pah-todo-exclude))
>    org-make-tags-matcher((quote org-pah-todo-exclude))
>    org-tags-view((4) (quote org-pah-todo-exclude))
>
>  It seems like the evaluation order is at fault, but I couldn't get  
> further.

indeed, currently the match entry is not evaluated.  I guess we could  
do that, but it would involve changing several functions.  I would  
need a convincing use case before I invest the time.  How would you  
want to use this?

- Carsten


[-- Attachment #1.2: Type: text/html, Size: 2568 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-09-28  5:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 23:16 Help with agenda-custom commands Paul Holcomb
2008-09-28  5:16 ` Carsten Dominik [this message]
2008-09-30 16:40   ` Paul Holcomb
2008-10-01  9:01     ` Carsten Dominik
     [not found] <E1KkzuK-0007T4-Uc@box188.bluehost.com>
2008-10-01 13:19 ` Robert Goldman

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=F7DA25EC-0D9E-474D-B7C0-9325590010F5@uva.nl \
    --to=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=pholcomb@cpoint.net \
    /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).